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

With no annotations, the description carries the behavioral disclosure burden. It mentions 'offline', which tells the agent no network calls are made, and 'autodetecting direction', which is a key behavioral nuance. It does not cover error handling or ambiguous inputs, but the disclosed traits go beyond the minimal schema.

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 a single concise sentence that front-loads the core function and unique behavior. Every word contributes meaningful information, with no 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?

The tool is simple, has one optional parameter, and an output schema exists, so the description does not need to explain return values. However, it lacks guidance on the q parameter format and behavior with ambiguous inputs, which could lead to misuse. The 'offline' and autodetect traits add useful context, but the overall description leaves some operational details uncovered.

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?

The input schema defines a single 'q' parameter with no description and schema description coverage is 0%. The description implies q is either an integer string or base36 string, but it does not explicitly state the expected format for encoding versus decoding, nor how the default empty value is handled. This is a significant gap.

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 ('Encode'), a resource ('int <-> base36'), and a distinguishing trait ('autodetecting direction'). This clearly separates it from sibling codecs like base32, base58, and base64 without needing to inspect schemas.

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 intended use is implied by the tool name and 'Base36 Codec' label, but there are no explicit statements about when to choose this over alternatives like base64 or base_convert. No exclusions or conditions are provided, leaving the agent to infer usage from context.

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