Skip to content

Trajectory and tool evaluators

Softprobe role: Softprobe does not implement this family as a Softprobe evaluator. Use a framework that already owns these checks, pin it as a RunnerVersion, and capture the native result bundle. See Ecosystem method families.

Trajectory evaluators assert on canonical OTLP steps: tools used, argument shapes, ordering, step count, efficiency, and goal-success proxies.

What they measure

CheckExample
Tool usedAgent invoked approved API tool, not raw HTTP
Args shapeTool args match expected schema
OrderingDiagnosis before remediation suggestion
Step count / efficiencyFewer redundant tool loops
Policy complianceNo forbidden tools in sandbox eval

Required evidence

  • Canonical ordered trajectory derived from OTLP spans
  • Span selectors: generation, tool, retriever, guardrail, sub-agent
  • Optional baseline trajectory for diff-style checks

Example measurements

MeasurementEvaluator
agent.tool_policy_complianceAllowed tools only
agent.trajectory_efficiencyStep count vs oracle bound

Selectors address spans without re-parsing raw OTLP per scorer. See Evidence and trajectories.

Resembles

DeepEval trajectory metrics (via adapter), custom tool-use checks in agent benchmarks.

Extension rule

Ship or pin a framework runner that already owns this method family. Do not add Softprobe scorer plugins, Softprobe Measurement schemas, Softprobe reducers, or Softprobe human-evaluator runtimes.

See Ecosystem method families and Framework runners.

Zero code changes · Full-context visibility · Cost optimization