pig_latin_convert

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds only the bidirectional capability and nothing on edge cases (e.g., non-alphabetic input, already-converted text, capitalization handling), which for a text transform is the meaningful behavioral gap.

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?

A single front-loaded sentence with no filler; both modes are stated in one clause each and nothing is wasted.

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?

For a simple pure-function text tool with full schema coverage, annotations, and no output schema, the description gives enough to invoke correctly. Minor gap is that the return value shape is never implied, but that is reasonable for a one-string transform.

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% and both parameters are documented in-schema, including the decode default. The description restates the decode direction but adds no format, encoding, or case-handling semantics beyond 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?

States a specific verb and resource ('convert text to Pig Latin') and adds the reverse direction via decoding. It is clearly distinguishable from neighboring text tools like rot13_convert or reverse_text, though it does not explicitly name them.

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?

Usage is implied by the two-direction phrasing, but there is no explicit guidance on when to use this versus other text-transformation siblings or when to set decode vs. leave it default. An agent can infer it, but nothing is spelled out.

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