base32

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

States read-only and no side effects, consistent with readOnlyHint annotation. Adds details about default JSON output and raw option. No contradiction with annotations.

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?

Concise but not ultra-tight. Six sentences covering main points without redundancy. Could be slightly shorter but maintains clarity.

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 complexity (8 params, no output schema), description covers return format (JSON/raw), encoding behaviors, and references to other tools. Adequately complete for agent usage.

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 baseline is 3. Description adds minimal parameter context beyond schema (e.g., mentions --raw but schema already describes raw). Does not significantly enhance semantic understanding.

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 'Encode or decode base32 data from files or stdin'. Differentiates from siblings by mentioning base64 for compact encoding and basenc. Provides specific verb-resource pair.

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 states use case: 'Use for human-friendly encoding (avoids ambiguous characters).' And when not: 'Not for compact encoding — use base64'. Lists alternatives: base64, basenc.

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