write_multi_sheet

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

With no annotations provided, the description carries full burden but only states what the tool creates, not how it behaves. It doesn't disclose whether the tool overwrites existing files, requires specific permissions, handles errors, or has performance characteristics. 'Create' implies a write operation, but no further behavioral details are given.

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?

Single sentence that efficiently communicates the core functionality without unnecessary words. Every element ('complex Excel file', 'multiple sheets', 'formulas', 'inter-sheet references') contributes directly to understanding the tool's purpose.

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 tool with 3 parameters, no annotations, and no output schema that creates complex Excel files, the description is insufficient. It doesn't explain what happens if the file already exists, what the return value is, error conditions, or limitations. The absence of annotations means the description should provide more behavioral context than it does.

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 100%, providing complete parameter documentation. The description adds minimal value beyond the schema by mentioning 'multiple sheets, formulas, and inter-sheet references' which aligns with the sheets and sheetReferences parameters, but doesn't provide additional semantic context or usage examples.

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 ('Create') and resource ('complex Excel file') with specific features ('multiple sheets, formulas, and inter-sheet references'). It distinguishes from basic write_file by specifying Excel capabilities, but doesn't explicitly differentiate from other Excel-related siblings like add_sheet or format_cells.

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 on when to use this tool versus alternatives like write_file (for simpler files) or add_sheet (for adding to existing files). The description implies it's for complex Excel creation but doesn't provide explicit usage context or prerequisites.

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