Add a tab

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

The description adds behavioral details beyond the schema by noting the return of the new tabId and the optional nesting behavior. However, with no annotations provided, it does not disclose any side effects, permission requirements, or default behavior (e.g., tab placed at end unless index specified), leaving some ambiguity.

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 two sentences, front-loads the primary purpose, and uses no redundant wording. Every sentence contributes essential information.

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 tool with 5 parameters and no output schema, the description provides the core action and return value but omits details such as the 'account' parameter, default placement behavior, and any prerequisites/errors. It is adequate for a simple add operation but not fully complete.

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 description clarifies the purpose of 'index' and 'parentTabId' by mentioning position and nesting, but these already have descriptions in the schema. It does not add meaning for required parameters 'documentId' and 'title', which lack schema descriptions, leaving a coverage gap.

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 uses a specific verb ('Add') and resource ('new tab to a Google Doc'), clearly distinguishing from sibling tools like rename_tab and delete_tab. It also mentions the return value (tabId), which clarifies the operation's outcome.

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?

The description states the tool adds a tab and optionally allows setting position and parent tab for nesting, providing context for how to use it. However, it does not explicitly mention alternatives or when not to use the tool, so it falls short of full guidance.

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