configure_worksheet_style

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

No annotations are provided, so the description carries full burden. It implies a mutation ('Apply'), but doesn't disclose whether changes are reversible, if it requires specific permissions, or what happens to unspecified style properties. The description mentions visibility toggles but doesn't clarify if these are additive or replace existing settings.

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, efficient sentence that front-loads the core purpose. Every word contributes to understanding the tool's scope without redundancy or unnecessary elaboration.

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?

For a complex mutation tool with 21 parameters, 0% schema coverage, no annotations, and an output schema (which helps but isn't described), the description is inadequate. It doesn't cover parameter meanings, behavioral implications, or usage context, leaving significant gaps for an AI agent to correctly invoke this 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?

With 21 parameters and 0% schema description coverage, the description only mentions 4 general categories (background color, axis/grid/border visibility) out of many parameters. It doesn't explain the purpose of parameters like 'pane_cell_style', 'label_formats', or 'axis_style', leaving most parameters semantically undocumented.

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 target ('worksheet-level styling'), with specific examples of styling aspects (background color, axis/grid/border visibility). It distinguishes this as a styling tool, but doesn't explicitly differentiate from potential styling-related siblings like 'configure_chart' or 'apply_color_palette'.

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 is provided on when to use this tool versus alternatives. With many sibling tools (e.g., 'configure_chart', 'apply_color_palette', 'add_worksheet'), the description doesn't indicate whether this is for initial setup, updates, or specific worksheet types, nor does it mention prerequisites like needing an open workbook.

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