int_convert

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the conversion dimensions available (hex/dec/bin/oct, 8/16/32/64-bit, signed/unsigned, endianness, ASCII), which is genuinely useful context, but says nothing about error handling, precedence when both value and values are supplied, or result structure.

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 tightly packed sentences with the capability list front-loaded and the routing hint second. No filler or redundancy.

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 stateless conversion tool with 100% schema coverage and no output schema, the mode coverage is decent, but the return value shape and the batch-vs-single precedence are left unaddressed. Adequate but with clear gaps.

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 both parameters are already documented in the schema with example formats. The description adds no syntax or format guidance beyond that, making the baseline 3 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?

Specific verb (converts) plus resource (integer(s)) and a concrete list of output bases and bit widths. It also names the sibling batch_calc and the condition that selects it, so an agent can separate the two without opening schemas. Only reason it isn't a 5 is that it doesn't clarify which of the near-neighbor codec tools (data_codec, ieee754_convert) it supersedes.

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?

Explicitly says to use batch_calc 'for several operations or chained steps in one call', which routes the agent away from int_convert for multi-step work. No explicit when-not for its own single/batch params, but the alternative condition is clear.

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