close_all_tabs

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

With no annotations, the description carries full burden. It discloses that the tool is destructive ('tears down the session') and mentions that opening a tab afterward starts a fresh session, implying session termination. However, it lacks specifics on whether state is saved or how the confirmation behaves.

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 concise, using three clear sentences. The first sentence states the action, the second provides usage context, and the third describes the return value. No wasted words.

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?

Given the tool has no parameters, a simple return of a short confirmation, and clear context from sibling tools, the description is fully complete. It explains both the mechanism (closing all tabs) and the reason (automatic shutdown cleanup).

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 tool has zero parameters, so no parameter description is needed. The baseline for no parameters is 4, and the description does not add or subtract from that.

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 tool closes ALL persistent browser tabs at once, tearing down the browsing session. It distinguishes from the sibling 'close_tab' which closes individual tabs, making the purpose unique and specific.

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 explicitly says 'You normally do not need this; the agent calls it automatically on shutdown', providing clear guidance on when not to use it. It implies that for individual tab closures, 'close_tab' should be used, though it does not explicitly mention that alternative.

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