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

With no annotations provided, the description carries full burden but fails to disclose key behaviors: does it output all variants at once or just one? It does not mention edge-case handling (e.g., non-ASCII, spacing), and there is no clarity on the return format. The phrase 'convert into ... variants' is ambiguous as to whether all are returned together.

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 that conveys the full scope of the tool with zero filler. Every word contributes to understanding what the tool does.

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?

Given the tool's low complexity (one parameter, no output schema), the description adequately states purpose and scope. However, the ambiguity regarding whether multiple case variants are returned at once and the lack of usage guidance leave gaps in completeness that a slightly richer description could fill.

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 input schema already provides a complete description for the single 'text' parameter ('Text to convert'). The tool description adds no additional parameter meaning, so the baseline of 3 is appropriate.

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 uses a specific verb ('Convert') and resource ('text') and explicitly enumerates the six case formats (slug/kebab, snake_case, camelCase, PascalCase, CONSTANT_CASE, Title Case), clearly distinguishing it from sibling text tools like hash_text or base64_codec.

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 the tool's context of use (text case conversion) but provides no explicit guidance on when to choose this tool over alternatives, nor any exclusions or prerequisites. It is assumed but not stated.

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