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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real behavior: free on testnet with no payment or wallet, unknown names return result="unknown" plus up to 3 did_you_mean suggestions, and empty detail fields are omitted rather than returned blank.

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?

Front-loaded with the free/testnet constraint, then the payload contents in one dense but scannable clause. The field enumeration is justified because no output schema exists, though the long parenthetical chain is slightly run-on.

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?

With no output schema, the description carries the return-value burden and does so thoroughly: headline, authoritative status, derived maturity, steward, details, dates and up to 3 sources, plus the unknown-name response shape. An agent has everything needed to call it and interpret results.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema: that 'protocol' accepts names covering protocols, platforms, wallets and stablecoins alike, and that list_protocols is the authoritative name source. It reinforces rather than merely restates the parameter docs.

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 gives a specific verb+resource (a 'fuller answer for ONE Ledger row') and enumerates exactly which entities qualify (protocol, platform, wallet, stablecoin) plus the returned fields. The word 'fuller' implicitly positions it against the sibling get_status, so an agent can distinguish them without opening schemas.

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?

It states the exact context (retrieve detail for one named Ledger row), documents the failure path for unknown names, and routes discovery to a named sibling ('Call list_protocols to see every name'). It does not explicitly state when to prefer get_status over this tool, so the alternative is only implied by 'fuller answer'.

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