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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description goes beyond them with genuinely useful operational context an agent cannot get elsewhere: the call costs $0.001 USDC per successful call via x402 on Solana, and the same operation is reachable over HTTPS at the listed endpoint.

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 core predicate comes first, followed by compact examples, the domain, and then payment/transport details. Nearly every sentence earns its place, though the example triplets could be trimmed to one positive and one negative case.

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?

The tool has one parameter, full annotation coverage, and no output schema, so most of an agent's needs are met — including cost and endpoint. The remaining gap is that the return format (a boolean) is only implied by 'whether', and the description never routes the agent to the several near-identical mcnugget_* siblings.

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 parameter meaning, and it partly does by making clear that n is a nugget count and restating the 0–5000 domain. However, the range merely repeats the schema's minimum/maximum, and the examples illustrate values rather than explaining units or edge-case behavior.

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 decision ('whether n nuggets can be ordered') with the exact box sizes 6, 9, and 20, which is far more informative than the bare name 'mcnugget'. It does not, however, distinguish itself from the sibling tools mcnugget_ways, mcnugget_count, mcnugget_min, and mcnugget_miss, which all concern the same Frobenius/coin problem.

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 worked examples (0, 6, 44 can; 1, 11, 43 cannot) implicitly convey the semantics of the boolean answer, but the description never says when to pick this tool over mcnugget_ways or mcnugget_min. Usage must be inferred from the name and siblings rather than stated.

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