apply_workbook_repairs

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

The description says 'safe' workbook repair actions, which contradicts the annotations' destructiveHint=true. The tool may be destructive, yet 'safe' is used without qualification. This is a direct contradiction and gives the agent misleading safety expectations.

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, front-loaded sentence that conveys the core action and key features. It is concise, though the word 'safe' is misleading and slightly wasteful.

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?

The tool has six parameters and no output schema, and the description leaves important context unexplained, such as what repair_types are expected, how sheet_names is used, or what the diff output contains. The mention of dry-run and diff is helpful but insufficient for a complex 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 0%, and the description does not explain any of the six parameters (filepath, dry_run, header_row, sheet_names, repair_types, sample_limit). Only 'dry-run planning' hint at dry_run, but no semantic detail for the others.

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 uses a specific verb ('apply') and resource ('workbook repair actions'), and clearly distinguishes itself from sibling tools like plan_workbook_repairs by focusing on execution. It also notes dry-run planning and diff output, further defining its scope.

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 after planning through 'dry-run planning' but does not explicitly state when to use this tool versus plan_workbook_repairs or diff_workbooks. No alternatives or exclusions are mentioned, so guidance is only implicit.

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