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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description goes beyond them by disclosing an operational constraint the annotations cannot express: the '(Cost: 1 credit)' charge, plus a hint at return contents (converted string, base names, exact decimal values). It omits the edge-case behavior (invalid digits, values exceeding base range) that would be the natural next addition.

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?

Two sentences, front-loaded with the core capability before the parameter and cost notes. Minor waste: the title is restated verbatim ('Number Base Converter: Number Base Converter converts...'), and the cost tag is buried at the end rather than surfaced.

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, side-effect-free three-parameter computation tool with a full output schema and complete schema descriptions, the description supplies everything needed to call it correctly: what it does, the base range, which parameters are optional, and the credit cost. Return-value details are correctly left to the output schema.

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 all three parameters are already documented with examples and a default, which sets the baseline at 3. The description adds only the 2–36 valid range and the fact that 'from' and 'to' are optional; it does not clarify value format (prefixes like 0x/0b, case sensitivity, negative numbers).

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?

Uses a specific verb and resource: 'converts numbers between any base from 2 to 36,' and enumerates the common bases (binary, octal, decimal, hexadecimal) to disambiguate what 'base' means. It does not name or distinguish itself from near-neighbors like UnitConverter, RomanNumeralConverter, or NumbertoWords, so an agent gets no sibling routing help.

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?

Usage is only implied by 'Pass a value with optional source and target bases' — there is no statement of when to prefer this tool over the other conversion tools in the catalog, nor any exclusion such as non-integer or negative inputs. An agent can infer the basic call pattern but not the boundary conditions.

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