set_cell_shading_docx

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

No annotations are provided, so the description carries the full behavioral burden. It never states that this mutates/saves the document, whether the target file or table must already exist, or what happens when row/col are null versus specified (implied whole-table scope). For a write tool with zero annotation coverage this is a real gap.

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?

A single front-loaded sentence with no filler; the action, scope, and the HEX format example are all packed efficiently.

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 5-parameter mutation tool with no annotations and 0% parameter documentation, one sentence is inadequate. Although an output schema exists (so return values need not be explained), the targeting semantics of row/col/table_index and the mutation/persistence behavior are missing.

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% across 5 parameters. The description adds meaningful format detail only for color_hex ('E0E0E0' or '#E0E0E0') and hints that row/col/table_index select the scope, but leaves file_path, table_index indexing base, and the exact row/col null semantics unexplained.

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?

States a specific verb (apply shading / background color) and resource (cell/row/column/table), so it is clearly distinguishable from neighbors like set_table_borders_docx or set_cell_alignment_docx. It does not explicitly name any sibling it must be chosen over, which keeps it just short of a 5.

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?

Usage is implied by the action itself — apply shading when you want background color. There is no explicit when-to-use/when-not, and no routing guidance such as how it relates to set_table_style_docx or set_table_borders_docx, which an agent must infer.

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