apply_text_style

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It doesn't disclose that this is a mutation operation (applies formatting changes), potential side effects, permission requirements, error conditions, or how it interacts with existing formatting. The description only covers targeting methods without behavioral context.

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 perfectly concise with two sentences that each earn their place. The first sentence states the core purpose, and the second explains the targeting methods. No wasted words, and information is front-loaded appropriately.

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?

Given the tool's complexity (14 parameters, mutation operation) with no annotations and low schema coverage, the description is incomplete. While it explains targeting methods well, it lacks crucial context about mutation behavior, error handling, and interaction with other formatting tools. The presence of an output schema helps, but the description should do more for a formatting mutation tool.

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 only 14%, so the description must compensate. It adds significant value by explaining the two targeting approaches (range vs. text search) and their corresponding parameters, which clarifies the semantic relationship between start_index/end_index and text_to_find/match_instance. This goes well beyond the minimal schema descriptions.

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 verb ('apply') and resource ('character-level formatting to text'), specifying formatting types like bold, color, font. It distinguishes from sibling tools like 'apply_paragraph_style' by focusing on character-level formatting, though it doesn't explicitly name alternatives.

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 implies usage by explaining two targeting methods (range or text search), which suggests when to use each approach. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'format_matching_text' or 'bulk_update_google_doc', nor does it mention prerequisites or exclusions.

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