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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful non-structural context: pricing ($0.001 USDC per successful call), the x402/Solana payment mechanism, and an alternate HTTPS endpoint. Missing only details like whether failed calls are charged.

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?

Four short sentences, each carrying distinct information (definition, examples, bounds, pricing/endpoint). Front-loaded with the core definition. Slightly dense on transaction details but nothing is pure filler.

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?

No output schema exists, and the description conveys the return value through worked examples plus the input bound. An agent has enough to call it correctly; only tangential details (e.g., behavior on out-of-range n) are absent.

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%, and the sole parameter is the integer n. The description compensates by stating the valid range (1 to 100000) and giving concrete input/output examples (n=10 → 32, n=30 → 266), which convey both the domain and the meaning of the result.

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 computational verb and resource: 'the sum of Hofstadter-Conway terms a(1) through a(n)'. This clearly distinguishes it from sibling hof_conway (single term) and other hof/hofstadter sum tools without needing to open the schema.

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?

The description gives the valid domain of n (1 to 100000) and example outputs, which implies usage, but never says when to choose this over hof_conway (single term) or hofstadter_sum. No explicit exclusions or alternative routing.

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