add-excel-table-rows

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

Annotations already indicate destructiveHint=true, which matches the tool's action of adding rows. The description does not add new behavioral insights beyond what annotations provide, such as permission requirements or side effects. The tip about values is more relevant to parameter semantics than behavior.

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 but includes a confusing and unnecessary first sentence ('Create new navigation property to rows for drives'). This wastes space and reduces clarity. The tip is succinct and 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?

The tip addresses the critical constraint that values must match the number of columns. However, the description does not explain other parameters like driveId, driveItemId, workbookTableId (beyond path parameter labels), nor does it mention the return value or error handling. Given 83% schema coverage, the description partially compensates but leaves 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?

The tip provides a concrete example of the body.values format (array of arrays), which adds significant clarity beyond the schema description that only states 'The raw values of the specified range. The data returned could be of type string, number, or a Boolean.' This helps the agent understand the structure required.

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 begins with a confusing phrase 'Create new navigation property to rows for drives' that does not clearly state the tool's purpose. The tip clarifies 'Adds rows to a table', but the overall purpose is muddled and does not effectively differentiate from sibling tools like 'update-excel-table-row' or 'insert-excel-range'.

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?

No guidance is provided on when to use this tool versus alternatives such as 'list-excel-table-rows' or 'delete-excel-table-row'. The tip focuses on input format but lacks usage context, leaving the agent to infer appropriate scenarios.

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