cleanup_browser

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

With no annotations provided, the description carries the full burden of disclosing behavior. It states 'Close all browser windows and clean up resources' but does not explain side effects such as potential data loss, whether the cleanup is permanent, or if it affects other browser sessions. The vague 'clean up resources' leaves undefined what exactly is cleaned and whether the action is reversible.

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 a single sentence with no filler or redundancy. It is appropriately front-loaded, immediately stating the primary action 'Close all browser windows' followed by the secondary resource cleanup. This is an efficient and well-structured description.

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 simple tool with no parameters and no output schema, the description provides the core purpose. However, contextual gaps remain regarding the relationship with sibling tools (e.g., whether it must follow initialize_browser), optional behavior (e.g., whether it only closes current session windows), and potential consequences. The description is minimally complete but not fully self-sufficient.

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 accepts zero parameters, and the input schema is empty with no properties. Thus, the schema coverage is 100%, and the description need not clarify parameters. The baseline of 4 for zero-parameter tools applies, and the description adds no unnecessary parameter clutter.

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's action: 'Close all browser windows and clean up resources.' This distinguishes it from siblings like initialize_browser (which starts the browser) and clear_conversation (which affects conversation data), making the purpose explicit and unambiguous.

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 provides no guidance on when to use this tool or scenarios where it should be avoided. It does not mention that it should be invoked after browser automation or before other operations, nor does it reference any alternative tools. Without usage context, the agent must infer the usage solely from the tool name.

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