create-excel-table

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

The description adds behavioral context beyond annotations by explaining error conditions (invalid address, overlap) and how the address maps to the worksheet. While annotations already indicate destructiveness, the description provides useful specifics.

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 concise with no wasted words. It front-loads the purpose and includes a helpful tip, making every sentence valuable.

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?

Given the complexity of the tool (nested body, multiple params) and no output schema, the description covers the essential aspects: purpose, error conditions, and usage context. It could mention the response shape, but the tip and examples compensate.

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?

The description adds meaning for the 'body' parameter, explaining the roles of 'address' and 'hasHeaders', and provides an example. For other parameters, the schema already provides descriptions, so overall coverage is good.

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 a new table') and the resource ('table'), with specific details on how the address determines the worksheet. It also distinguishes from sibling tools like add-excel-table-rows by mentioning that this tool is a prerequisite.

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 tip explicitly states that this tool is required before using add-excel-table-rows/update-excel-table-row/delete-excel-table-row on a plain-cells sheet, providing clear context for when to use it. It does not explicitly say when not to use it, but the guidance is strong.

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