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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior nontrivial. The description adds value beyond those annotations by explaining that the operation is deterministic, that it reports material differences, and that it is a paid resource with a specific price. This is useful behavioral context, though return format and side-effect details remain unspecified.

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?

The description is three sentences with no fluff: core behavior, intended use/negative scope, and pricing are each given exactly one sentence. Core behavior is front-loaded, making it easy for an agent to scan and act.

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 0% schema parameter coverage first-class and no output schema, the description leaves significant gaps: it does not explain path syntax for ignore_paths/required_paths, how numeric_tolerance applies, what a 'material difference' looks like, or what the response contains. Annotations help with safety but not with calling semantics.

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 for all parameter meaning. It only explains the required parameters by name ('expected and observed values') and vaguely references 'caller-supplied verification rules' without defining ignore_paths, required_paths, or numeric_tolerance. The optional parameters remain semantically opaque.

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 states a specific behavior: deterministic comparison of expected vs observed values and reporting of material differences under caller-supplied rules. It also scopes the intended domain ('trust identity permission / quality unknown') and excludes several adjudication contexts rich enough to differentiate from many sibling verification tools, though it does not explicitly distinguish between the multiple trust_identity_permission_verification_* siblings.

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 positive intended context ('Intended for trust identity permission / quality unknown') and explicit exclusions ('Do not use for legal, identity, sanctions, fraud, contractual, or regulatory adjudication'). This provides clear when-to-use and when-not-to-use guidance, though it does not name specific alternative tools.

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