Number base convert

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

Annotations already cover read-only, idempotent, and closed-world behavior, so the description adds useful context about input auto-detection, ignored separators, negative handling, and the additional bit-length/two's-complement output. It does not discuss error behavior for malformed inputs, but the added behavioral detail is substantial.

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 main purpose and key constraints are front-loaded in one dense paragraph. It is appropriately sized for the tool's complexity, though the run-on structure and the website URL are slightly less essential than the core behavior.

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?

With no output schema, the description does a good job summarizing the return surface: primary base conversions plus bit length and two's-complement details at 8/16/32/64 bits. It could be more explicit about the exact output shape, but it is complete enough for an agent to call correctly.

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 baseline is 3. The description adds that values are arbitrary-size BigInts and reiterates prefix/separator handling, but most parameter meaning is already documented in the schema.

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 and resource: convert a whole number of any size between bases 2–36. It includes scope detail (BigInt, binary/octal/decimal/hex/base 36) and the extra two's-complement view, so an agent can distinguish it from unrelated calculator or byte-conversion siblings.

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?

It gives clear context for use: whole numbers only, auto-detection from 0x/0b/0o prefixes, ignored separators, and negatives allowed. It also explicitly excludes fractions, though it does not name a sibling alternative such as calc_fraction, so it falls short of full when/when-not/alternatives guidance.

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