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

Annotations already declare readOnlyHint/idempotent/non-destructive, and the description goes beyond them with real operational facts: batch ceiling of 100 strings, smart acronym/digit splitting, Title Case small-word behavior, accent transliteration for slugs, and crucially a per-call price ($0.001 USDC via x402 on Solana) that an agent must know before invoking. It stops short of describing what a call actually returns.

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?

One dense paragraph, front-loaded with the format list — the highest-value information first. The format enumeration is long but each item adds capability information; the trailing price/endpoint sentence is short and useful. Minor bloat from listing all formats inline.

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?

There is no output schema, so the description should explain the return shape — e.g. whether to='all' returns a map keyed by convention, and what happens when both text and texts are supplied. Those gaps are material for a 5-parameter tool; the payment and batch details partially compensate.

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 0%, so the description must carry semantics. It effectively maps most `to` enum values (camel, Pascal, snake, SCREAMING_SNAKE, kebab, Train, dot, path, Title, Sentence, slug) and hints at `texts` maxItems via 'Up to 100 strings'. But it never explains the choice between `text` and `texts`, the 'all' default, or the purpose of `slugMaxLength` and `slugSeparator`, leaving three of five parameters undocumented anywhere.

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?

Specific verb (convert) plus resource (identifiers and phrases between naming conventions), with all thirteen target formats enumerated. An agent immediately knows this is a case-formatting/transliteration utility and can tell it apart from the numeric or hash siblings.

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 (naming-convention conversion, slug generation, batch up to 100) and notes the HTTPS alternative endpoint, but never states when to prefer this over plausible siblings like format_convert or text_clean, nor any exclusions. Usage is inferable rather than stated.

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