set_text_case

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

Discloses the three case options and effect of 'none', but lacks details on whether operation is destructive, idempotent, or requires existing runs; no annotations provided.

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?

Purpose stated in first sentence, parameter descriptions follow in efficient list format; no wasted words.

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?

Covers input parameters well but omits prerequisites (e.g., document must be open, run must exist) and error conditions; output schema assumed sufficient but not shown.

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?

Adds full meaning beyond schema titles: explains para_id, zero-based run_idx, and case values with examples; schema coverage 0% makes description essential.

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?

Description uses specific verb 'set' and resource 'text case transformation on a run', clearly distinguishing from siblings like set_run_color or set_run_font.

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 (e.g., set_run_font for letter spacing) or exclusions; usage context is implied but not explicit.

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