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

Annotations already declare readOnly/idempotent/non-destructive/non-open-world, so the safety profile is covered. The description adds genuinely new behavioral context: it returns all rows unfiltered, it is free on testnet, and it deliberately returns only name/aliases/status rather than full detail.

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, front-loaded with the cost note and return-shape, closing with the routing pointer. No filler and nothing that restates the tool name.

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 by naming the three returned fields and signaling the result set is complete ("Every row"). Ordering and response shape/format remain unspecified, a minor gap for a zero-param list tool.

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?

The tool takes zero parameters, which is the baseline 4 case. The schema has 100% description coverage and there is nothing for the description to clarify about inputs; "Every row" does confirm the absence of filter arguments.

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 resource (every row in the human-verified Ledger) and enumerates exactly what it returns: name, aliases and status. It is distinguishable from get_status/get_status_detail by being the unfiltered catalog rather than a per-entity lookup.

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?

"Use a name from here with get_status or get_status_detail" explicitly states the downstream workflow and which siblings consume its output. It lacks an explicit when-not clause (e.g., don't call this to check a single entity), so it stops short of full routing guidance.

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