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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine domain context beyond the annotations by saying the proof runs from the strategy's chain head to a day's root anchored on Solana, but it omits error behavior (missing attestation for a date) and whether the proof is deterministic.

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 short sentence-fragment with zero padding, which is efficient, but the terseness comes at the cost of a verb and any operational detail. It is under-specified rather than deliberately lean.

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 need not be explained, but for a two-required-parameter lookup tool the description leaves the date/strategy_id formats, failure modes, and any linkage to a verification workflow unstated. An agent could not call this correctly on the first attempt without guessing at formats.

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 0%: neither parameter has any description. The phrase 'that day's root' and 'a strategy's chain head' loosely map to date and strategy_id, but the agent gets no date format (ISO date? epoch?), no strategy_id format, and no constraints, so the description does not compensate for the coverage gap.

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 names the resource (a Merkle proof from a strategy's chain head to the day's anchored root) but is a noun phrase with no verb, so the agent must infer 'retrieves/returns' from the tool name. It is specific about what the artifact is, yet never distinguishes it from siblings like verify_object or get_envelopes, which also deal with proof/verification concepts.

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 statement of when to call this versus alternatives, no prerequisite (e.g., an attestation must exist for that date), and no mention of what to do if no proof is available. The agent is left to infer usage entirely from the tool name.

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