excel_write_range

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write and destructive profile is carried by structured data. The description adds only that the worksheet must already exist; it says nothing about what overwrite=false does to occupied cells, how styling flags (bold, fillColor, numberFormat) alter the sheet, or that omitting outputPath mutates the source file in place.

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?

One tight, front-loaded sentence with no filler or repetition. It is well structured but under-specified rather than padded, which is a completeness problem rather than a verbosity one.

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 9-parameter destructive write tool with 22% schema coverage and no output schema, a single sentence covering none of the optional styling, overwrite, or output-path parameters is far too thin. An agent cannot determine in-place vs. new-file behavior or collision semantics from this definition.

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 only 22% across 9 parameters, so the description must compensate and largely does not. 'Rectangular matrix of values' loosely clarifies the shape of the values array, but overwrite, bold, fillColor, numberFormat, startCell and outputPath get no explanation beyond the bare schema.

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 gives a specific verb ('Write'), a specific resource ('XLSX worksheet'), and constrains the payload ('rectangular matrix of values'). It does not, however, distinguish itself from close siblings such as excel_set_formulas or excel_native_batch, so an agent must infer the boundary from the name alone.

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 single phrase 'existing XLSX worksheet' implies the target file must already exist, but there is no explicit when-to-use guidance, no pointer to excel_create_workbook for new files, and no mention of when excel_set_formulas or excel_native_batch would be preferred.

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