Delete a tab

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

With no annotations, the description carries the full burden of disclosure. It transparently reveals cascading deletion of child tabs and the safety verification mechanism using expectTitle. It doesn't mention permanence or permission requirements, but covers the most important destructive behaviors.

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?

Two sentences, front-loaded with the action and key detail (cascade), followed by the essential safety constraint. Every word earns its place without fluff.

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 delete tool with no annotations and no output schema, the description covers the action, the cascade behavior, and a critical prerequisite. It doesn't describe the return value or any cleanup details, but the tool is relatively simple and the provided context is sufficient for correct invocation.

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 50%, and the description compensates by explaining the purpose and criticality of expectTitle, and clarifying that tabId is the identifier. However, documentId and account parameters lack meaningful explanation beyond the schema, so the value added is partial.

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 clearly states the action ('Delete a tab') and the specific resource (by tabId), and uniquely distinguishes it from sibling tools like add_tab and rename_tab. It also adds the cascading behavior, which is specific to this delete operation.

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 implies when to use the tool (when deleting a tab) and provides a crucial usage requirement: expectTitle must come from list_tabs. However, it doesn't explicitly mention alternatives or when not to use it, such as if child tabs should be preserved.

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