change_case

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

With no annotations provided, the description carries full behavioral disclosure. It explicitly reveals auto-backup behavior, the meaning of backup=False, atomic validated saving, and refusal of Word-open documents. This is strong, actionable transparency beyond what the schema alone provides.

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 compact and information-dense, with no filler. Each sentence contributes a distinct fact: transform values, targeting modes, backup behavior, and operational constraints. Key information is front-loaded with the purpose first.

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 tool with no annotations and five parameters, the description covers most operational essentials: transforms, targeting, backup, save behavior, and a Word-open refusal. The main gap is the default behavior when neither indices nor find is provided, and how conflicts between the two targeting modes are resolved. The presence of an output schema mitigates the need to describe return values.

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 has 0% description coverage, so the description must compensate. It explains transform values, target selection via indices or find, and backup semantics. It does not fully clarify what happens if both indices and find are supplied, or if neither is supplied, but it otherwise gives meaningful meaning to the parameters.

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 identifies the operation as changing text case, with explicit transform values (upper, lower, title, sentence). It does not explicitly distinguish itself from sibling tools like format_text or replace_paragraph_text, but the specific verb and transform set make the purpose unmistakable.

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 gives clear targeting guidance: use paragraph indices or every case-insensitive occurrence of `find`. It also states a key operational constraint (refuses documents open in Word). It stops short of saying when to prefer an alternative sibling tool, but the scoping rules are clear enough for most calls.

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