append_excel_table_rows

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

Annotations already mark destructiveHint=true; description adds 'expand its range safely' as a behavioral guarantee but does not detail potential structure changes, how safety is ensured (e.g., allow_structure_change), or what conditions might cause failure. No contradiction, but value beyond annotations is limited.

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 concise sentence with the core action and a safety qualifier; no wasted words.

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 an 8-parameter mutation tool with no output schema, the description is insufficient: missing alternatives, parameter semantics, and behavioral edge cases. Sibling tools and safety controls are not mentioned.

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%, so description must explain parameters; it only hints at 'rows' and 'native Excel table' but leaves sheet_name, dry_run, include_changes, allow_structure_change, and expected_structure_token undefined in meaning.

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?

Description uses specific verb 'Append' and resource 'native Excel table' with 'expand its range safely,' clearly distinguishing it from sibling tools like append_table_rows by emphasizing native tables and safe range expansion.

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?

Description implies usage for native Excel tables needing range expansion but does not explicitly state when to use vs alternatives such as append_table_rows or upsert_excel_table_rows. No exclusions or when-not guidance.

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