num_convert

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

Discloses key behaviors: accepts 0x/0b/0o and minus sign, prefixes non-decimal output, pad_bytes zero-fills minimally, bit-aligned, rejected for decimal, arbitrary precision. No annotations provided so description carries full burden and does so thoroughly.

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 main sentences plus a third for pad_bytes and a final note on arbitrary precision. Every sentence adds unique value. Front-loaded with the core purpose.

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?

Given 4 parameters, no output schema, and no annotations, the description covers all essential aspects: input format, base selection, padding rules, edge cases (decimal rejection), and performance (arbitrary precision). No 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 coverage is 0%, but description adds significant meaning beyond parameter names: explains how 'value' is parsed, that from_base/to_base are dials for conversion direction, and that pad_bytes pads but never truncates and is rejected for decimal. Fully compensates for lack of schema descriptions.

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?

Clearly states verb 'convert' and resource 'big-integer between bases'. Specific about supported bases (hex/dec/bin/oct). Distinguishes from sibling tools which are more about encoding/hashing rather than base conversion.

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?

Provides clear context: how to parse value, handle prefixes, sign, and pad_bytes behavior. However, no explicit when-to-use or when-not-to-use compared to siblings, nor alternatives listed.

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