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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only that pagination is supported; it says nothing about auth requirements, rate limits, or the leaf count/shape. With annotations carrying the burden, a 3 is warranted.

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 short sentences, front-loaded with the operation and followed by the pagination note. No filler, though the second sentence is thin enough that it borders on restating the schema.

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 simple read-only list tool with an output schema absent, the definition is minimally viable but leaves the free-form query object unexplained (no pagination key names) and gives no hint about what a Merkle leaf record contains. Given the sibling merkle tools, more routing context would be expected.

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 coverage is reported at 100%, so the baseline is 3. The description's note that pagination parameters are supported hints at the query object's purpose, but the query schema is a free-form additionalProperties bag with no named pagination keys, and the description does not supply any of them (offset, limit, cursor).

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?

States a specific verb and resource (list leaves of the Merkle audit tree), which cleanly separates it from affix_merkle_root (root) and affix_merkle_proof (proof generation). It stops short of naming those siblings, but the noun 'leaves' is specific enough for an agent to route correctly.

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 when-to-use guidance and never references the numerous sibling merkle tools (affix_merkle_audit, affix_merkle_audit_batch, affix_merkle_proof, affix_merkle_root). An agent gets no signal for choosing this over affix_merkle_audit.

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