add-excel-table-rows

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, signaling a write operation. The description adds the constraint that values must match the number of columns, but omits details like append behavior, error handling, or idempotency.

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 short with only two sentences, but the first sentence is unclear and could be removed. The tip is useful and front-loaded, making the overall structure efficient despite the initial confusion.

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 tool's complexity (6 parameters, nested body, no output schema), the description covers the body format well but does not explain return values or provide context for the path parameters (driveId, driveItemId, workbookTableId). Annotations partially mitigate missing behavioral details.

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 descriptions cover the path parameters and body properties thoroughly (83% coverage). The description adds value by providing a concrete example of the values array format and clarifying that each inner array represents a row, which aids understanding beyond the schema.

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 main description 'Create new navigation property to rows for drives' is vague and seems like boilerplate. However, the tip clarifies that it adds rows to a table, so the purpose is discernible after reading the entire description. It distinguishes from sibling tools like update-excel-table-row and clear-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 explicit guidance on when to use this tool versus alternatives like update-excel-table-row or insert-excel-range. The tip includes an example body format but does not provide context for appropriate use cases or prerequisites.

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