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

The description fully discloses behavioral traits: 'Read-only and deterministic: it returns the transformed string and changes nothing, safe to call repeatedly.' Since no annotations are provided, this carries the full burden and does so excellently, covering side effects and repeatability.

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 two sentences, front-loaded with the purpose and operations. The second sentence adds usage and behavior. Every word earns its place; no redundancy or fluff.

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 with an output schema, the description covers the tool's purpose, valid inputs, behavior, and usage. The output schema likely documents the return value, and the description explicitly states it 'returns the transformed string'. Complete for its complexity.

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?

The schema defines text and operation as plain strings with no enums. The description lists all valid operation values (UPPERCASE, lowercase, camelCase, etc.), which is essential parameter semantics that the schema lacks. It does not elaborate on the exact behavior of each case type, but the list is sufficient for basic use.

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 function with a specific verb and resource: 'Apply an exact, deterministic text transformation.' It enumerates all supported operations, making it unambiguous. The sibling tools are all color-related, so this text tool is immediately distinguishable.

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?

Provides explicit guidance: 'Use whenever exact, reproducible case formatting matters rather than rewriting the text by hand or guessing the casing.' This gives a clear context of use and a contrast to manual alternatives, though it does not name specific alternative tools (none exist among siblings).

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