browser_close

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

No annotations are provided, so the description carries the full burden. 'Close the page' gives no indication of side effects (e.g., whether the session is invalidated, whether the operation is destructive, or if it can be undone). For a mutating action, this lacks essential behavioral transparency.

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 short phrase, which is appropriately sized for a simple tool. It is front-loaded and contains no wasted words. However, it is slightly too minimal, providing no context beyond the core action.

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?

With no output schema and no annotations, the description 'Close the page' is too incomplete. It fails to explain what occurs to the session, whether the session remains open, or any prerequisites. For a tool with a required sessionId, more context is needed for reliable 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 coverage is 100% (one parameter, sessionId, is documented with a description). The tool description adds no additional meaning beyond the schema. Per the rubric, a high schema coverage yields a baseline of 3, and no compensation is needed.

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 'Close the page' uses a specific verb and resource, clearly indicating the action of closing the browser page. It is distinct from siblings like close_session which likely closes the session, though it doesn't explicitly differentiate. The purpose is clear enough for a simple tool.

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 gives no guidance on when to use this tool versus alternatives such as close_session, browser_navigate, or browser_navigate_back. It provides no context or exclusions, so the agent is left without direction on choosing this tool.

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