conversion_number_base

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

Annotations already provide readOnlyHint, destructiveHint, and idempotentHint. The description reinforces these with 'read-only, non-destructive, offline, no auth' and adds that it returns a converted string plus an analysis block. This adds context beyond the annotations without contradiction. Slight deduction because some behavioral traits (e.g., exactly what the analysis block contains) are not detailed, but the description is sufficient given annotation coverage.

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 sentences, front-loaded with the core purpose, followed by usage guidance and behavioral context. Every sentence earns its place with no redundancy or wasted words.

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 tool with 4 parameters (100% schema coverage), no nested objects, and an existing output schema, the description covers the tool's purpose, usage scope, behavioral traits, and return structure (converted string + analysis block). It is fully complete for an agent to understand how and when to use it.

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 coverage is 100%, so the baseline is 3. The description does not add significant meaning beyond the schema; it mentions that decimal/octal values must be 0-1114111, which is already in the schema's from_format description. No additional parameter details are provided.

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 between five textual encodings (ASCII, binary, hex, decimal, octal) as sequences of byte/codepoint values. It distinguishes from siblings like conversion_base_converter (single integer arbitrary radix), conversion_binary_decimal (signed/unsigned with bit width), and conversion_decimal_hex (two's complement). The verb 'convert' and the specific resource (five encodings) are explicitly defined.

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 provides explicit guidance on when to use this tool ('when you need to move character data across base representations') and when not to, naming three specific alternatives. It also notes that the tool runs locally, is read-only, offline, requires no auth, and has default rate limits, helping the agent understand invocation context.

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