convert_case

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, but it only states the basic conversion action. It does not explain how input text is parsed, how edge cases are handled, or what 'and more' includes, leaving significant behavioral ambiguity.

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 sentence, front-loaded with the action verb, and lists formats efficiently. Every word serves a purpose, with 'and more' compactly covering the remaining schema enum values without unnecessary repetition.

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 with two required parameters and no output schema, the description adequately conveys the core purpose and supported formats. However, it omits details about return type and how the tool handles ambiguous or mixed-case input, which are minor gaps given the tool's simplicity.

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 coverage is 100% with both parameters described, so the baseline is 3. The description restates some enum values as human-readable case names but adds no additional semantics beyond what the schema already provides for the 'text' and 'to' parameters.

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 explicitly states 'Convert text between' with a specific list of case formats, making the tool's purpose unmistakable. The verb 'convert' and resource 'text' are clear, and the enumerated formats distinguish it from sibling tools like encode or slugify.

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 gives no guidance on when to use this tool versus alternatives, nor does it mention any context or exclusions. It only implies usage by listing conversion formats, which is not enough for an agent to decide between this and related tools like slugify.

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