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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the operation (encode/decode) but does not clarify that ROT-13 is symmetric (encoding and decoding are the same operation), nor does it mention any edge cases, input restrictions, or output format. The behavioral transparency is minimal and leaves room for misinterpretation.

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 a single concise sentence with no unnecessary words. It is appropriately front-loaded with the tool name and function. However, it is so brief that it sacrifices essential details, which reduces its effectiveness despite the efficient 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?

For a tool with a single parameter and no annotations, the description is incomplete. It fails to explain what the parameter 'q' expects, what the output format is, or how the encode/decode behavior works in practice. The presence of an output schema is noted but not described, leaving gaps in the agent's understanding.

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 0% and the description does not mention the single parameter 'q' at all. The schema only provides the type and default, with no explanation of what 'q' represents. The description adds no semantic value to the parameter, leaving the agent to guess that it is the input string.

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 clearly states the tool's function: 'ROT-13 encode/decode' with the explicit resource 'ROT-13 Cipher'. It distinguishes this from sibling ciphers like rot47, caesar, and atbash by naming the specific algorithm. The verb 'encode/decode' is precise and unambiguous.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, exclusions, or comparisons to sibling cipher tools. The usage is only implied by the tool's name and description, not explicitly stated.

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