get_proof

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what the tool returns (complete proof bundle with specific components) which is valuable context beyond the input schema. However, it doesn't mention performance characteristics, error conditions, authentication requirements, or rate limits, which would be helpful for a retrieval operation.

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 perfectly structured: a clear purpose statement followed by return value details, then parameter documentation. Every sentence earns its place with zero waste. The information is front-loaded with the core functionality stated first.

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 the tool has an output schema (which handles return value documentation) and only one parameter, the description provides adequate context. It explains what the tool does, what it returns, and documents the parameter with an example. For a simple retrieval tool, this is reasonably complete, though additional behavioral context would improve it.

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?

The schema has 0% description coverage, so the description must compensate. It provides a clear explanation of the single parameter ('proof_id') including its purpose and an example format ('prf_20260310_143022_a1b2c3'), adding significant meaning beyond the bare schema. The example format helps users understand the expected input pattern.

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 states the specific action ('Retrieve') and resource ('full cryptographic proof for a given proof ID'), distinguishing it from siblings like 'certify_call' (create), 'get_usage' (usage stats), and 'verify_proof' (validation). The verb+resource combination is precise and unambiguous.

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 implies usage context by specifying 'for a given proof ID', suggesting this tool is for retrieving existing proofs rather than creating or verifying them. However, it doesn't explicitly state when to use this versus alternatives like 'verify_proof' or provide exclusion criteria, leaving some ambiguity about tool selection.

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