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

There are no annotations, so the description carries the full burden of behavioral disclosure. It indicates a mutating operation but does not disclose what happens if a sheet with the same title already exists, whether changes are reversible, or what response is returned.

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?

A single, front-loaded sentence that directly states the operation and target. There is no filler or redundant restatement of the tool name.

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 mutating operation with no annotations, no output schema, and sparse parameter documentation, the description is too minimal. An agent would benefit from knowing failure behavior, whether the tab is created at a specific position, and any permission or mailbox requirements beyond the mailbox parameter description.

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 coverage is only 33%, so the description must compensate. It does provide some semantic mapping: 'worksheet tab' suggests what 'title' is for, and 'existing workbook' contextualizes 'workbookId'. However, it adds no detail on constraints, uniqueness, or format 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 description states a specific verb and resource: 'Add a new worksheet tab to an existing workbook.' It clearly distinguishes from creating a new workbook (create_excel_workbook) and from the Google-sheet equivalent (add_google_sheet_tab), though it does not name those alternatives explicitly.

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 when-to-use or when-not-to-use guidance is provided. The phrase 'existing workbook' implies the workbook must already exist, but it does not explain prerequisites, such as creating the workbook first or checking list_excel_workbooks for a valid workbookId.

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