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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the mutation/safety profile is covered. The description adds nothing on top: it doesn't say what happens if a tab with the same title already exists, where the new tab is positioned, or whether the workbook 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 with no filler, and the scope qualifier ('existing workbook') lands immediately. It is efficient, though its brevity is partly the source of the missing detail rather than pure conciseness.

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 three-required-parameter mutation tool with no output schema and only one-third of parameters documented, the description is too thin. It omits the mailbox/workbook scoping requirements and any mention of the sibling Google Sheets equivalent.

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 only 33% — just the mailbox parameter is documented, and even that only points at list_authorized_mailboxes. The description does not explain what 'title' controls (tab name, uniqueness constraints) or how 'workbookId' is obtained, so it fails to compensate for the low coverage.

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 ('Add') and resource ('a new worksheet tab') scoped to 'an existing workbook', so the operation is unambiguous. However, it never distinguishes itself from the near-identical sibling add_google_sheet_tab, leaving the agent to infer the Excel-vs-Google-Sheets split from the tool name alone.

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?

There is no guidance on when to use this versus add_google_sheet_tab, nor any prerequisite about the workbook needing to already exist beyond the phrase 'existing workbook'. No exclusions or alternatives are named.

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