apply_table_cell_style

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

No annotations are provided, so the description must carry the full burden. It states the tool applies a paragraph style to all cells but gives no details about side effects (e.g., overwriting existing styles), error conditions, or behavior if prerequisites are not met. This leaves significant gaps for an AI agent.

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 short (two sentences) and front-loaded with the purpose, but it lacks detail on parameters and behavior, making it efficient yet incomplete. It earns a middle score.

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 modifies table cells and has three parameters with no annotation coverage, the description is too minimal. It does not explain return values (though output schema exists), prerequisites beyond the sequence hint, or edge cases. The agent would have to infer too much.

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%, and the tool description does not explain any parameter. It only mentions style names in examples but not how to specify them or the role of table_idx and document_handle. The agent receives no added meaning beyond the field names.

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 a paragraph style to every cell in a table') and gives concrete examples like 'TableText' and 'Table-Text'. It distinguishes itself from siblings such as 'apply_style_to_range' and 'set_table_style' by specifying it applies to every cell in a table.

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 explicitly says to use after 'add_table + copy_table_style' to match template formatting, providing a clear usage context. While it doesn't mention when not to use or list alternatives, the guidance is actionable and specific.

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