Convert a number between bases such as binary, octal, decimal, hexadecimal, or any base from 2 to 36. Specify source and target bases to transform values accurately.
Convert a number between bases (binary, octal, decimal, hex, or any base 2-36).
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes | The number to convert (as string). | |
| to_base | No | Target base (2-36, default 16). | |
| from_base | No | Source base (2-36, default 10). |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the supported base range but does not explain output format, invalid-input behavior, or whether the returned value is a string.
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 front-loaded sentence with no wasted words. It states the operation and the allowed base range immediately.
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 three-parameter conversion tool with full schema coverage and safety annotations, the description is nearly complete. The main remaining gap is that there is no output schema and the description does not state what the conversion returns.
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 100%, so the schema already documents value, to_base, and from_base, including defaults. The description restates the base range but adds no further parameter semantics such as accepted digit characters or case sensitivity.
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 a specific verb and resource: convert a number between bases, with concrete base examples and the 2-36 range. It does not distinguish this tool from the sibling number_base_convert, which appears to serve a near-identical purpose.
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 to use it by naming supported bases, but it gives no explicit when-not guidance and does not route the agent away from similar siblings such as number_base_convert or other convert_* tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.