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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the value is account-scoped and 'current' (implying it changes as receipts accrue), but says nothing about whether it is a snapshot, how it is consumed, or any caching/rate considerations.

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 no filler, which is the right shape for a simple read. It is arguably too terse for a tool sitting in a crowded Merkle family, but nothing in it is wasted.

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?

Annotations cover the safety profile and the lack of an output schema is partly mitigated by 'root' being self-describing. Still, no guidance on how this relates to the other Merkle endpoints leaves an agent guessing in exactly the situation where disambiguation matters most.

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 nominally 100%, but the single 'query' parameter is an opaque pass-through object with no named properties, and the description never references it. Baseline 3 applies since the schema technically documents the parameter, though neither source explains what query keys are meaningful.

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 (get the Merkle audit-tree root) and scopes it to the account's proof receipts, so the agent knows exactly what is returned. However, with five Merkle siblings (affix_merkle_audit, affix_merkle_audit_batch, affix_merkle_leaves, affix_merkle_proof, affix_merkle_verify_proof) it makes no attempt to distinguish itself from them, leaving ambiguity about which Merkle endpoint to pick.

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?

There is no when-to-use guidance, no prerequisite, and no mention of alternatives, despite a dense cluster of similar Merkle tools. The agent must infer that this is the lightweight root-only call versus the full audit endpoints.

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