calculate_number_base_convert

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

No annotations provided. The description claims support for bases 2,8,10,16, but the schema allows any integer for from_base and to_base without validation details. It does not cover error handling, input format requirements, or return type specifics beyond 'Returns converted number'.

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 two sentences long, front-loading the core purpose and supported bases. It includes a cross-reference to an auxiliary tool without unnecessary detail.

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?

With an output schema present, the description covers the basic conversion purpose and references related tools. However, it lacks details on input constraints, error scenarios, and behavioral traits that would be needed without annotations.

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?

The input schema has 100% coverage for all three parameters. The description only restates them ('value, from-base, to-base') and adds that conversion is 'between bases 2,8,10,16', which provides minimal extra meaning beyond the schema.

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 clearly states the tool converts numbers between bases 2, 8, 10, and 16, with specific examples. It mentions programming context and inputs/outputs. However, it does not distinguish itself from the sibling 'calculate_base_converter' or other conversion tools.

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 says 'Use for programming' and suggests 'See list_bundles for related conversions calculators'. This provides some context but does not explicitly state when not to use this tool or what alternative tools exist beyond the bundle reference.

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