convert_number_base

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

No annotations provided; description carries full burden. Discloses parameter defaults and ranges but does not mention error behavior for invalid input or output format. Adequate but not comprehensive.

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?

Very concise: purpose in first sentence, usage scenarios, then clean parameter list. No unnecessary words, front-loaded.

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?

Given output schema exists, description doesn't need to detail return values. Covers tool purpose, usage context, and parameter semantics. Missing potential detail on input validation but adequate for a simple conversion tool.

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 has 0% description coverage; description compensates by explaining each parameter: num as 'The number string to convert', from_base with default and range, to_base with default and range. Adds meaning beyond schema types and titles.

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?

Description clearly states 'Convert numbers between different bases (hex, decimal, octal, binary)' with specific verb and resource. Provides use case examples like data inspection, color values, memory addresses. Distinguishes from sibling tools like binary_convert by indicating general base conversion.

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?

Gives context for usage ('low-level data inspection, color values, or memory addresses') but lacks explicit when-not-to-use or alternatives to sibling tools like binary_convert. No exclusion criteria provided.

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