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

With no annotations provided, the description carries the full burden. It discloses that the tool operates offline and attempts all 25 shifts, which is useful context. However, it does not specify the input/output format, whether it returns all shifts or a best guess, or how the parameter is interpreted.

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 extremely concise and front-loaded with the core functionality. It avoids unnecessary words and quickly conveys the tool's purpose. It lacks structured sentences but is appropriately sized for the simplicity of the tool.

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 one optional parameter and no annotations, the description is incomplete. It fails to explain what 'q' represents or what the output looks like (though an output schema exists). The offline and all-shifts details help, but the missing parameter semantics leaves a critical gap for an agent to call it correctly.

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 0% description coverage for the single parameter 'q', and the description does not explain it at all. It is not stated that 'q' is the ciphertext to be decoded, leaving the agent to infer its purpose from the tool name and context. This is a significant gap given the schema offers no guidance.

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 a specific function: Caesar Cipher brute force over all 25 shifts. It uses the verb 'brute force' and identifies the resource (Caesar cipher), distinguishing it from siblings like rot13, rot47, and vigenere which handle different cipher types or single shifts.

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 implies usage for Caesar cipher decryption via brute force, but it does not explicitly state when to choose this over alternatives or mention exclusions. The term 'offline' suggests a local operation, but there's no guidance on scenarios where this tool is preferred over other cipher tools.

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