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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful scope context about what the desk info covers, but does not disclose additional behavioral traits such as whether the data is static or up-to-date, or how the response is structured.

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?

The description is a single, well-structured sentence that front-loads the topic and enumerates specific information dimensions. Every listed item adds value and there is no filler or repetition.

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 read-only, zero-parameter informational tool with rich annotations and no output schema, the description sufficiently explains what an agent will learn by calling it. It covers the key content areas and leaves no ambiguity about the tool's purpose or input requirements.

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 has zero parameters, and schema description coverage is 100%, so there is nothing for the description to add about parameters. A baseline of 4 is appropriate because parameter semantics are trivially complete.

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 clearly identifies the resource (the Dead-Coin Buyback Desk) and explains what content the tool provides: supported chains, pricing tiers, discount model, quote TTL, and quote->reserve->settle flow. It does not explicitly contrast itself with sibling get_deadcoin_quote, but the informational scope is unmistakable.

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?

No guidance is given on when to use this tool versus alternatives. Since get_deadcoin_quote is a sibling and likely the transactional counterpart, the description would benefit from a sentence like 'For a live quote, use get_deadcoin_quote instead.' The current text only describes content, not selection criteria.

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