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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile needs no restating. The description adds one behavioral fact — the default of returning every style when none is requested — but that fact is already duplicated in the schema's 'style' description, so the net new information is limited.

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?

Two sentences, zero filler, with the capability set front-loaded and the default behavior stated last. Nothing needs to be trimmed.

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?

With a full output schema present, return values need no explanation, and the description covers purpose and default behavior adequately. A minor gap remains: it never notes the per-line conversion semantics (only present in the schema) or the 100k length cap, though those are documented elsewhere.

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%, so the baseline is 3. The description names only 6 of the 16 enum values (omitting lower, upper, sentence, capital, pascal, dot, path, train, alternating, inverse) and adds no format or edge-case semantics beyond what the schema already documents for text and style.

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?

States a specific verb (Convert) and resource (text) plus concrete output styles (camelCase, snake_case, kebab-case, CONSTANT_CASE, AP/Chicago title case), which is far more informative than the title alone. An agent can distinguish this from neighbors like convert_units, convert_data_format, or convert_color at a glance.

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 via 'Returns every style unless one is requested', which tells the agent that omitting 'style' is a valid call. However, it gives no guidance on when to prefer a single style, what to do for mixed/ambiguous input, or when a sibling tool (e.g. format_json) would be more appropriate. Usage is only implied, not stated.

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