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

Annotations already declare readOnly/idempotent/non-destructive, so the description's contribution is the commercial and transport context: $0.001 USDC per successful call via x402 on Solana, and an equivalent HTTPS endpoint. That paid-call disclosure is exactly the kind of behavior an agent cannot learn from structured fields.

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, front-loaded with the definition and recurrence, then bounds, then pricing/endpoint. Every sentence adds distinct information with no 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, but the worked examples convey the return shape, and the recurrence plus bounds make the tool fully callable. The only gap is the absence of any mention of the closely named siblings that could be confused with this one.

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% (the single 'n' property has no description), so the description must carry the load, and it does: it establishes 1-based indexing, the valid range 1–100000, and two sample values (a(5)=3, a(10)=6) that let an agent sanity-check the result. It doesn't state the return type explicitly, but the examples make it unambiguous.

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 ('the nth Hofstadter-Conway term') with the exact recurrence and worked values, so an agent knows precisely what is computed. It does not distinguish itself from the many Hofstadter siblings (hof_conway_sum, hofstadter_conway, hof_female, hof_male), leaving ambiguity about which one to pick.

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?

Usage is implied by the sequence definition and the stated domain (n from 1 to 100000), which is enough for a single-argument pure-math call. There is no explicit routing guidance — nothing says to use hof_conway_sum for cumulative totals or how this differs from hofstadter_conway, despite those siblings existing.

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