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

Annotations declare idempotentHint=true and destructiveHint=false, and the description adds valuable behavioral detail: the result is deterministic, machine-readable, has bounded errors, and involves a 'receipted external execution.' This goes beyond the annotations without contradicting them.

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 compact sentences front-load the primary purpose and then summarize key output behavior. There is no filler, though the phrase 'receipted external execution' is jargon-heavy and slightly obscures meaning.

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?

An output schema exists, so return values do not need detailed explanation, and annotations cover safety characteristics. However, the description fails to illuminate the purpose of consumer_id and invocation_context, and the 'supported subset' of JSON Schema is left undefined. For a tool with four required parameters, this gap makes the description incomplete for an agent that must produce valid inputs.

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 only 25%, and the description compensates poorly. It indirectly maps 'supplied structured data' to the value parameter and 'customer-supplied JSON Schema' to the schema parameter, but consumer_id and invocation_context are completely unexplained in both the description and the schema, leaving critical required parameters ambiguous.

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 verb ('Validate'), the resource ('supplied structured data'), and the standard ('JSON Schema Draft 2020-12 supported subset'). This clearly differentiates it from siblings like evidence_verify and hash_compute, making the tool's core function unmistakable.

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 context is clear: use this tool when data must be validated against a customer-supplied JSON Schema. However, it does not explicitly name alternatives or state when not to use it, so it stops short of full usage guidance.

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