set_table_cell_shading

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Apply shading/filling' implies a mutation operation that modifies document content, but the description doesn't disclose whether this requires specific permissions, whether changes are reversible, what happens if the cell doesn't exist, or what the response looks like. For a mutation tool with zero annotation coverage, this is inadequate behavioral transparency.

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 extremely concise at just 6 words, with zero wasted language. It's front-loaded with the core action and target. Every word earns its place, making it easy to parse quickly. This is an example of excellent conciseness, though it may be too brief for complete understanding.

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 a mutation tool with 6 parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what happens when the tool executes, what errors might occur, what the return value is, or how to interpret the parameters. For a tool that modifies document content, this level of documentation is inadequate for safe and effective use.

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 0% schema description coverage for all 6 parameters, the description provides no information about what any parameter means or how to use them. The description mentions 'shading/filling' which hints at 'fill_color' and possibly 'pattern', but doesn't explain what values are acceptable, what 'table_index' refers to, or how indices work. The description fails to compensate for the complete lack of schema documentation.

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 shading/filling') and target ('to a specific table cell'), which is a specific verb+resource combination. It distinguishes itself from sibling tools like 'format_table_cell_text' or 'highlight_table_header' by focusing specifically on cell shading rather than text formatting or header highlighting. However, it doesn't explicitly mention how it differs from other table formatting tools like 'format_table' or 'apply_table_alternating_rows'.

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 doesn't mention prerequisites (e.g., document must exist, table must exist), when not to use it, or what alternatives exist for similar functionality. Given the many sibling tools for document manipulation, this lack of contextual guidance is a significant gap.

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