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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the value is treated as a string representation and bases are limited to 2-36. However, it omits output form (string vs number), digit/case conventions, negative or fractional handling, and error behavior on invalid digits.

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?

A single sentence with zero filler, front-loading the action and the input constraint. Every clause earns its place.

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 pure, stateless conversion tool with no output schema and no annotations, the description is nearly sufficient but leaves return format and invalid-input handling unspecified. It is minimum-viable rather than complete.

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 compensate; it partially does by clarifying the base range (2-36) and that the value is a string representation. It adds nothing about the 'value' field's accepted characters, case sensitivity, or whether prefixes like 0x are tolerated, leaving the three nested fields under-specified.

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 verb and resource ('Convert a number's string representation') and adds the meaningful scope constraint of bases 2-36. It is clearly distinguished from numeric siblings like number_roman or number_words by naming base conversion, though it does not explicitly route against alternatives such as encoding_transcode.

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?

No when-to-use or when-not-to-use guidance is given. The description never mentions alternatives (e.g., unit_convert, encoding_transcode) or the conditions under which radix conversion is the right call, leaving the agent to infer usage entirely.

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