capitalize_text

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

The description accurately describes the simple transformation but lacks details on edge cases (e.g., handling of punctuation, numbers, or special characters). Annotations are not contradicted (readOnlyHint=false is consistent as it does not modify external state).

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 concise sentence with no redundant information, perfectly structured for quick understanding.

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 transformation with one parameter and no output schema, the description provides sufficient information. No additional details are needed.

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 input schema covers 100% of parameters with a description for 'text' that repeats the tool's purpose. The description adds no new meaning beyond the schema; baseline score 3 applies.

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 'Capitalize first letter of each word' clearly states the verb (capitalize) and resource (text). It distinguishes from siblings like convert_text_to_uppercase (which capitalizes all letters) and convert_text_to_lowercase.

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?

No guidance on when to use this tool versus alternatives such as convert_text_to_camelcase or convert_text_to_pascalcase. The description does not provide context for selection.

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