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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about output format, how invalid input is handled, whether prefixed strings like '0x1F' are accepted, or whether results are returned as strings or numbers. For a no-annotation tool this is a significant gap.

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 tight sentence with the core capability front-loaded and zero padding. It is appropriately sized, though it is sparse enough that it arguably under-specifies rather than over-truncates.

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 conversion utility with no output schema, the description covers the core purpose but omits input-format expectations (e.g. prefixes, negative numbers) and error behavior. Adequate but with clear gaps for a tool that takes arbitrary string input.

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 coverage is 67%: to_base and from_base are documented in the schema with defaults (16 and 10), while 'num' has no description. The description's mention of hex/decimal/octal/binary loosely hints at base values but never ties them to the parameters or explains that base codes must be integers. Baseline 3 given the schema does most of the work.

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 numbers between bases') and enumerates the common bases, so the agent knows exactly what operation is performed. It is distinguishable from siblings like convert_units or convert_currency by the 'bases' framing, though it doesn't explicitly name those alternatives.

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?

There is no when-to-use or when-not-to-use guidance, and no conditions under which an alternative sibling (e.g. convert_units) would be preferred. The description offers only the bare capability, leaving routing entirely to the agent's inference.

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