case_convert

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

With no annotations, the description carries full responsibility for behavioral disclosure, but it only states the core conversion action. It does not mention how input casing is detected, how non-alphanumeric characters are handled, whether spaces are treated as word delimiters, or any error behavior. This leaves significant ambiguity for edge cases.

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 front-loaded sentence that conveys the tool's purpose instantly. The '[PRO — 3 trial uses left]' note is slight extra but not damaging. Every word earns its place; no unnecessary filler.

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?

The tool is simple and the schema fully covers parameters, but there is no output schema or annotations. The description does not mention return value format or behavior with unusual inputs, which could matter for complete usage. It is minimally viable but lacking some contextual richness.

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%: both 'text' and 'to' have descriptive entries, and the enum for 'to' lists all acceptable values. The description adds no extra parameter meaning beyond what the schema already provides, so the baseline score of 3 applies.

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 explicitly lists all supported target formats (camelCase, snake_case, PascalCase, kebab-case, CONSTANT_CASE, Title Case), clearly distinguishing it from other text utility siblings. The function is 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?

No guidance is provided on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or context where another tool (e.g., slug, string_escape) would be more appropriate. The only extra note is a PRO trial limit, not usage context.

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