add_table

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

No annotations are provided, so the description carries the full behavioral burden, yet it only states that the table name and range are returned. It does not say whether an existing table in the range causes an error, whether source formatting is altered, whether the operation requires a selected/active worksheet, or that it is a workbook mutation.

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?

Two tight sentences with the action front-loaded and the return value second; no filler or redundancy.

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?

It usefully discloses the return payload, so no output schema is needed. But for an unannotated mutation tool with six parameters, it omits conflict/error behavior and any note about workbook targeting or side effects on the underlying range, leaving meaningful gaps.

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% and every parameter (name, range, style, sheetName, hasHeaders, workbookId) is documented inline, so the baseline of 3 applies. The description adds no parameter meaning beyond the schema, notably nothing about what happens when both name and sheetName conflict with existing tables.

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?

States a specific verb and resource ("Create an Excel table (ListObject)") and scopes it ("over a range"), which also disambiguates it from the Word sibling insert_table and from read_table/edit_table_columns. An agent can identify what this tool does in one read.

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?

There is no guidance on when to use this versus alternatives such as insert_table (Word), add_worksheet, or format_range, and no prerequisites are given (e.g. that the range must already contain header data, or which workbook is targeted). The only implied usage is the phrase "over a range".

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