set_text_case

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

No annotations exist, so the description carries the full burden. It explains the allowed case values ('upper', 'small', 'none') and that run_idx is zero-based. However, it lacks broader behavioral context such as reversibility, side effects, or error conditions. It does not contradict any annotations.

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 concise and well-structured: a single-line purpose followed by a bulleted argument list. Every sentence adds value, and there is no redundancy.

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?

The tool has 3 required parameters and an output schema (not shown), so the description focuses on inputs. It adequately describes all parameters but omits preconditions (e.g., ensuring the run exists) and does not differentiate from siblings. The description is minimally complete for a simple formatting tool but leaves gaps in usage context.

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 parameter explanations in the description are essential. It clarifies para_id as 'paraId of the target paragraph', run_idx as 'Zero-based index of the run', and explains the case values. This adds significant meaning beyond the raw schema, though it could hint at how to obtain para_id or run_idx.

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 purpose: 'Set text case transformation on a run.' It uses a specific verb ('set') and identifies the resource ('text case on a run'), which distinguishes it from sibling tools like set_run_font or clear_run_formatting.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention related tools such as set_run_font for other formatting or clear_run_formatting to remove all formatting, nor does it state when not to use it.

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