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

With no annotations at all, the description carries full burden, and 'Pure CPU, instant' does usefully disclose that this is a side-effect-free, non-network, non-rate-limited operation. However it says nothing about failure modes — invalid digits for the chosen base, negative values, zero, or whether output is uppercase/prefix-formatted — which matters for a parse-based utility.

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 purpose and then a single operational note. Every clause earns its place and there is no filler or repetition of the schema.

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 pure function with full schema coverage and no output schema, the description covers purpose, valid range, and cost profile. The remaining gap is output shape (digit case, prefixes) and invalid-input behavior, which are minor for a basic conversion tool.

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 'value', 'from', and 'to' with their defaults are already fully documented in structured data. The description adds nothing beyond that baseline — no note on case sensitivity, leading '0x' prefixes, or sign handling — so it sits exactly at the baseline 3.

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 supplies a specific verb ('Convert'), resource ('an integer'), and an explicit valid domain (bases 2-36), so an agent immediately knows the operation. It falls short of 5 because the sibling list contains near-duplicates ('convert_number_base', 'binary_convert', 'base32', 'base64') and the description never marks the boundary between them.

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?

Only the input domain (integer, bases 2-36) implies when the tool applies; there is no explicit when-to-use statement and no reference to the overlapping siblings an agent must choose between. Nothing tells the agent whether to prefer 'convert_number_base' or 'binary_convert' instead.

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