case_convert

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

No annotations are provided, so the description carries the full burden. It discloses that the tool converts text into multiple case styles and that the response can be limited, but it does not describe the return format, what happens with invalid case names, or edge cases like empty strings or Unicode handling.

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 that front-loads the purpose, enumerates the case styles, and provides a usage hint. Every word earns its place with no redundant content.

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 two-parameter tool, the description covers the main functionality and optional parameter usage. However, since there is no output schema and no annotations, the lack of information about the return value structure (e.g., a map of case style to converted text) or behavioral edge cases leaves noticeable gaps.

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?

With 0% schema description coverage, the description compensates well by explicitly identifying the `text` parameter (as the input text) and the `cases` parameter (as an optional limiter), additionally listing the valid values. This goes beyond the bare schema and gives practical meaning.

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 purpose with a specific verb and resource: 'Convert text into multiple case styles in one call.' It lists the exact case styles, immediately distinguishing it from sibling text utilities like slugify or text_cleanup.

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 clear context about when to use the tool (when you need multiple case conversions in one call) and hints at usage with 'Pass `cases` to limit the response,' but it does not explicitly mention when not to use it or suggest alternative tools for specific needs.

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