Excel Create Workbook

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

The description says 'Create', which is a state-changing write operation, while annotations declare readOnlyHint=true. This is a direct contradiction. The description also omits any behavioral context about permissions, overwrite behavior, or location selection.

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 a single clear sentence that front-loads the action and resource. There is no wasted text.

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?

For a creation tool with a contradictory annotation, the description leaves out important behavioral context such as how the target location is chosen, what happens if the file already exists, and whether credentials/permissions are needed. The output schema reduces the need to describe return values, but the overall guidance is still thin.

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 fully documents all four parameters. The description adds minimal value beyond the schema, only hinting that the destination is OneDrive or SharePoint.

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 states a specific verb ('Create') and resource ('new Excel workbook (.xlsx)'), and clearly locates the action in OneDrive or SharePoint. It is easily distinguished from sibling tools like excel_create_table or excel_add_worksheet.

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 given about when to use this tool versus alternatives, nor are exclusions or prerequisites mentioned. The agent must infer usage from the tool name and one-line description.

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