apply_paragraph_style

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

The description says 'Apply' implying a mutation, but provides no details on side effects (e.g., overwriting existing style, effect on entire paragraph or range, authorization needs). With no annotations, the description carries full burden for behavioral disclosure but falls short.

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 waste. However, it could benefit from slight expansion without losing brevity. Still effective.

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?

With 5 parameters (2 required) and no output schema, the description is too brief. It does not mention that the style must already exist, or what happens to the text beyond style application. Given the complexity, more completeness is warranted.

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?

All 5 parameters are described in the input schema (100% coverage), so the description does not need to add much. It does not elaborate on startIndex/endIndex usage or relationships (e.g., applying to a range vs. whole paragraph). Baseline 3 is appropriate.

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 action ('apply') and the resource ('paragraph style') and target ('text'). It distinguishes itself from siblings like 'create_paragraph_style' and 'find_replace_text' as an application of an existing style.

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 other style-related tools (e.g., 'create_paragraph_style', 'apply_color'). No prerequisites mentioned (e.g., style must exist, text frame must be selected).

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