Encode a document to TOON

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful behavioral context beyond them: the output is text, the format is line-oriented, and it is a drop-in substitute for JSON that mcptoon can serve. It does not discuss size/limits or failure behavior, but with strong annotations a 4 is fair.

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?

Efficiently front-loaded: the core function leads, followed by usage conditions and sibling routing in a single flow. The trailing ellipsis indicates the description is truncated mid-sentence, which slightly undercuts an otherwise tight structure.

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?

An output schema exists, so explaining the return value is unnecessary, and annotations carry the safety profile. The description covers purpose, usage, and alternatives adequately; only the truncated tail and lack of any error/limit behavior keep it from a 5.

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% with a single required parameter whose escaping/leniency behavior is documented in the schema itself. The description adds no syntax or format detail about the payload beyond what the schema provides, so the baseline 3 applies.

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 (converts/encodes) and resource (a JSON document into TOON), and explicitly distinguishes itself from two named siblings: compare_formats and decode_toon. An agent can identify this as the standalone encoder without opening any schema.

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 when to use it ('when you need the encoded form by itself') and routes to the two alternatives with their distinguishing conditions: compare_formats for side-by-side savings, decode_toon for the reverse direction. Nothing is left to inference.

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