set_text_case

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

Without annotations, the description must disclose behavior. It states the action and the effect of each case value (upper=all caps, small=small caps, none=remove). However, it omits potential side effects (e.g., overriding other formatting), error conditions (e.g., invalid run index), and whether the operation is reversible.

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: one main sentence followed by a structured 'Args:' list. Every line is informative. Front-loaded with the core action. No unnecessary 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?

The description covers parameter semantics well but lacks broader context. It does not mention required document state, error handling, or how this tool fits among many siblings (e.g., when to use set_text_case vs set_run_font). With an output schema present, return values not needed, but usage prerequisites are missing.

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?

Schema description coverage is 0%, but the description adds clear meaning for all three parameters. It explains 'para_id' as target paragraph ID, 'run_idx' as zero-based index, and 'case' with explicit mappings: upper to all caps, small to small caps, none to remove. This goes well beyond schema definitions.

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 'Set text case transformation on a run' with specific verb and resource. It distinguishes among sibling tools like set_run_color and set_run_font by targeting a specific transformation on a run. The parameter descriptions further clarify the target and options.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., document open, paragraph exists) or when to choose 'none' to remove a case transform. No comparison with other text formatting tools is given.

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