Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish read-only, open-world, idempotent, and non-destructive behavior. The description adds meaningful behavioral context: determinism, field-level diff semantics, the specific diff categories reported, hashes, required-path checks, and importantly what the tool does NOT prove (external truth, legal correctness, fraud, causal fault). It also discloses that it is a paid resource with a concrete price.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler. The first sentence front-loads the core behavior and output categories, and the second efficiently adds pricing and critical limitations. Every clause contributes information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given six parameters, zero schema descriptions, and no output schema, the description leaves meaningful gaps: it does not explain the meaning or constraints of max_diffs, ignore_paths, numeric_tolerance, or the output structure. The behavioral and pricing context is strong, but parameter semantics are under-specified for a tool an agent must call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It effectively clarifies 'expected' and 'observed' and hints at 'required_paths' via 'required-path checks', but it leaves 'max_diffs', 'ignore_paths', and 'numeric_tolerance' completely unexplained. An agent cannot understand the semantics of nearly half the parameters from the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly names the operation: a deterministic field-level evidence diff between expected and observed execution results, and specifies what it reports (missing, unexpected, type-changed, value-changed paths). It is specific about the resource and output categories, though it does not explicitly distinguish itself from the many execution-safety sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance about when to use this tool versus sibling tools such as execution_safety_verification_* or outcome_assurance_verification_*. It implies usage for diffing expected versus observed results, but offers no exclusions, alternatives, or scenario-based guidance. The limitation caveat is useful but is not usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.