Text ⇄ UTF-8 bytes

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

Annotations already establish readOnly, idempotent, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context the annotations cannot: lenient byte parsing and the fact that invalid UTF-8 is reported with U+FFFD replacements rather than erroring, which directly affects how an agent interprets results.

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?

Three tight sentences: purpose first, then the lenient-input caveat, then the edge-case behavior, with the reference URL last. Every sentence carries information an agent could act on, and nothing is padded.

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 carries return-value disclosure and does so partially: it says invalid UTF-8 is shown with replacements but does not state the overall return shape (e.g., that a string is returned in the chosen format). For a simple two-way conversion tool this is close to complete.

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 the baseline is 3. The description goes beyond the schema by giving concrete accepted byte-input examples ('48 65', '0x48,0x69', '01001000 01101001'), clarifying that the bytes parameter tolerates mixed notation — semantics the schema does not convey. The uppercase parameter is only covered by the schema, keeping it just below 5.

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?

States a specific verb and resource ('turn text into its UTF-8 bytes ... or bytes back into text') and enumerates the supported output formats. An agent can distinguish it from siblings like base64_encode/decode or base_convert because the description is explicitly about UTF-8 byte representation in hex/bin/dec.

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 bidirectional framing ('or bytes back into text') makes the two usage paths clear, and the lenient-input sentence tells the agent this tool accepts many byte input shapes. It does not, however, name when to prefer base64_encode or hash_compute over this tool, so the sibling routing is left implicit.

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