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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds meaningful context beyond those annotations: examples of return values, the valid input range, pricing at $0.001 USDC per successful call via x402 on Solana, and an HTTPS endpoint alternative. It does not contradict the annotations.

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 front-loaded with the core operation and examples, followed by range, pricing, and endpoint details. It is compact and has no filler, though the HTTPS endpoint line is somewhat auxiliary for an MCP tool description.

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 simple one-parameter, read-only mathematical tool with no output schema, the description provides enough context to invoke it correctly: input meaning, valid range, worked return-value examples, and pricing/access details. Sibling differentiation is not explicit, but the operation itself is fully specified.

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 parameter meaning, and it does: n is the number whose Hamming-sequence position is returned, with worked examples clarifying the mapping. The range 1 to 1000000000000 is also restated, though the schema already enforces it, and no additional format nuances are needed beyond that.

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 states precisely what the tool computes: the 1-based position of n in the Hamming sequence, returning 0 when n is not Hamming. The examples (1→1, 12→10, 36→20, 7→0) make the operation unambiguous and distinguish it from related Hamming sibling tools such as hamming_nth or hamming_next.

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 implies when the tool is useful by defining its exact output, but it does not explicitly name alternatives such as hamming, hamming_nth, or hamming_dist, nor does it state when not to use this tool. The range of n is provided, which helps constrain usage, but sibling routing is left to inference.

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