close_browser_session

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

The description clearly states the action (close a browser session), but lacks details on side effects, permissions, or cancellation of ongoing operations. No annotations are provided, so the description carries the full burden, which is only partially met.

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 short and front-loaded with '[LEGACY]', efficiently conveying purpose and deprecation. It earns its place, though it could be slightly more comprehensive without significant bloat.

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's simplicity (one parameter, no output schema, no nested objects), the description is adequate for a legacy tool with a clear alternative. However, it could be more complete by explaining the actual behavior of closing a browser session.

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 input schema has one required parameter 'session_id' with no description, and the tool's description does not provide any additional meaning. With 0% schema description coverage, the description should compensate but fails to do so.

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 that the tool closes a browser session, using a specific verb and resource. It also explicitly distinguishes itself from the sibling tool 'manage_browser_sessions' by recommending its use instead.

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 explicit guidance: 'Use manage_browser_sessions instead', indicating when not to use this tool and directing the agent to the preferred alternative.

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