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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral details beyond that: it uses BigInt for exact conversion of arbitrarily large numbers)Skip, and it returns the value in the requested base plus all four bases. These go beyond the safety profile and help the agent anticipate output shape and precision.

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 three short sentences plus a source link. Each sentence earns its place: purpose, BigInt exactness, return format. The source link is a useful reference. There is no fluff or redundant repetition of schema data.

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 low-complexity tool with full schema documentation, an output schema, and safety annotations, this description is complete. It covers purpose, precision, output, and source. Nothing essential an agent needs to select or call the tool correctly is missing.

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 parameter semantics are already fully documented in the schema. The description adds no additional parameter-level meaning beyond what is already provided (e.g., it does not clarify prefixes, negatives, or base names further). With full schema coverage, a baseline score of 3 is appropriate.

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 ('Convert'), a resource ('a whole number'), and a precise scope ('from one base to another between binary, octal, decimal and hexadecimal'). It also explains the return behavior ('plus all four bases'), making it fully distinguishable from other converter tools in the sibling list.

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 clearly limits usage to whole numbers and to the four named bases, providing clear context for when to use this tool. It does not explicitly name alternatives or exclusion conditions relative to other converter tools, but the scope is specific enough that an agent can infer appropriate usage.

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