rot13_cipher

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

No annotations are provided, so the description must explain behavior. It does not mention what happens to input text, whether it encodes or decodes, handles case, or supports non-ASCII characters. The cost mention is the only behavioral-ish detail, but it is unrelated to the tool's operation.

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 technically short, but it is under-specified rather than concise. It contains one sentence with a label and a cost note, neither of which helps an agent use the tool. It lacks the essential functional summary that should be front-loaded.

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 tool, a one-liner could suffice, but this one does not even say 'applies ROT13 to a string.' With no output schema and a generic input schema, the description leaves the agent completely in the dark about what to pass and what to expect. It is severely incomplete even accounting for the sibling context.

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 schema has a single generic 'params' object with no specific property descriptions. The description adds no explanation of what parameters the tool expects (e.g., 'text' or 'input'). Schema coverage is 100% for the top-level param, but that param is a generic catch-all; the description should compensate, but it does not.

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 merely states 'rot13 cipher' which essentially repeats the tool name, and labels it 'Other Utilities tool.' It does not state what the tool does (e.g., applies ROT13 rotation to text) and does not distinguish it from sibling ciphers like caesar_cipher or atbash_cipher. This is a vague purpose at best.

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?

There is no guidance on when to use this tool or why it might be preferred over other cipher tools. No use cases, exclusions, or alternatives are mentioned. The description is purely a label with cost info.

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