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

Annotations already cover read-only/idempotent/non-destructive, but the description goes further: it names the exact return contents (headline, status, last verified date, ONE source URL), states the missing-name fallback, and guarantees 'never a guessed answer'. The 'Free on testnet' note discloses cost/deployment context.

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?

Three tight sentences with no filler; the cost note and scope lead, then return shape, then the error path. Nothing is padded, though the lead sentence is fragmentary.

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 single-param read tool with full schema coverage and no output schema, the description is nearly self-sufficient: it conveys return fields, error semantics, and cost. Only the relationship to get_status_detail is missing.

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% and the schema already documents the protocol parameter with examples and the list_protocols hint. The description largely restates that same guidance, adding no format or syntax detail beyond the schema.

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: status of one Ledger row (protocol/platform/wallet/stablecoin), and enumerates the returned fields. It differentiates against list_protocols explicitly, but does not distinguish itself from its closest sibling get_status_detail, which an agent also needs to disambiguate.

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?

Tells the agent how to obtain valid input ('Call list_protocols to see every name') and describes the not-found path (result="unknown" plus did_you_mean). It stops short of saying when to prefer this over get_status_detail.

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