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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the POST endpoint noted in the description is consistent with readOnlyHint=false, so there is no contradiction. However, the description adds no behavioral context beyond that structural hint: it says nothing about authentication, whether the proof is consumed/witness state changes, or what a verification failure looks like.

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?

One front-loaded sentence with the endpoint in parentheses; nothing is wasted or buried. The terseness is a completeness problem, not a conciseness one.

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?

For a cryptographic verification tool with an unspecified request body and no output schema, the description is too thin: it never explains what the body must contain or what the verification result conveys. The agent cannot construct a correct call from this definition alone.

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?

There is a single 'body' parameter whose only schema text points at an external OpenAPI resource, so the actual field contract is opaque. With nominally 100% schema description coverage the baseline is 3, and the description contributes nothing about the required proof/root fields the caller must supply.

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 and resource: 'Verify a Merkle inclusion proof against the audit root', which is far more precise than the bare title. It implicitly distinguishes itself from siblings like affix_merkle_proof (generate) and affix_merkle_root (fetch root), though it never names those alternatives explicitly.

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?

No when-to-use guidance is offered beyond the endpoint path. There are several verification-flavored siblings (affix_merkle_proof, affix_proof_ref_verify, affix_circuit_verify, affix_aggregate_verify) and the description gives the agent no basis for choosing among them.

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