Excel Add Table Rows

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

The description says 'Append one or more rows, which is a mutating operation, yet annotations declare readOnlyHint: true. This is a direct annotation contradiction and could cause an agent to treat a write operation as side-effect-free. No behavioral context such as insertion semantics is provided beyond the schema.

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 one front-loaded sentence with a clear verb and object and no filler. It is appropriately sized for a straightforward append operation, though the misleading annotation prevents the overall definition from being fully trustworthy.

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?

Even with rich schema coverage and an output schema, the description fails to reconcile its mutating behavior with the readOnlyHint annotation. An agent relying on annotations would wrongly assume this operation is safe and read-only, so the definition is materially incomplete and potentially misleading.

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%, so the schema already documents all parameters. The description adds little beyond confirming rows can be one or more, which is baseline-level value and does not require extra compensation.

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 ('Append'), names the resource ('existing Excel table'), and specifies the payload ('one or more rows of data'). The word 'existing' clearly separates it from create_workbook and create_table siblings, so an agent can tell its purpose at a glance.

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 phrase 'existing Excel table' implies this tool is for adding rows to a table that already exists, which gives some contextual guidance. However, there are no explicit when-to-use or when-not-to-use instructions, and no alternatives are named, so the agent must infer selection logic from the sibling list.

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