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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add context — and it does: it discloses the paid access model ($0.001 USDC per successful call via x402 on Solana) and an equivalent HTTPS endpoint. Cost and payment flow are exactly the kind of operational detail annotations cannot express.

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?

Front-loads the definition, then examples, then the domain, then pricing and endpoint. Every sentence carries information; nothing is redundant or padded.

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-parameter pure-computation tool with no output schema, the description supplies the rule, the domain, sample outputs and cost, which is enough to call it correctly. The only gap is that it does not state the return type or what happens for invalid input, though the examples imply integer results.

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 0%, so the description must carry the load, and it does: it defines n as the index into the sequence, restates the 0..1000000 domain, and gives five worked mappings (n=0→0, n=3→5, n=5→17, n=6→20, n=8→64) that make the indexing convention unambiguous. It stops short of restating the integer type, but the examples resolve the intent.

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 Moser-de Bruijn number) and even gives the construction rule (binary digits of n read in base 4), which is far more than the bare name. It is distinguishable from sibling variants by naming 'nth', but it never explicitly contrasts itself with moser_check, moser_count, moser_index or moser_sum, leaving the sibling boundary implicit.

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 only implied: an agent can infer that this computes a single term for a supplied index. There is no explicit when-to-use statement, no mention of alternatives such as moser_index for the inverse mapping, and no note on error behavior for out-of-range input beyond the range itself.

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