Release a browser session

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

The description adds substantial behavioral detail beyond the annotations: it reports idempotency ('Safe to call twice'), destructive effects ('current URL and session-only page state are gone'), persistence rules, and return value ('reports the final URL and title'). This fully discloses the side effects and consequences of calling the tool.

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, front-loaded with the primary action ('Shut down the current browser and stop the meter'), then covers safety, side effects, persistence, and return behavior in four short sentences. Every sentence adds meaningful information without redundancy.

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 low-complexity tool with one parameter and no output schema, the description is complete: it covers the destructive nature, idempotency, persistence behavior, return value, and usage timing. Nothing needed for correct invocation or expectation-setting is omitted.

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 already provides 100% coverage for the single parameter, including 'Live session_id from steel_session_create.' The description does not need to add parameter-level detail, and it does not. Baseline score of 3 is appropriate because the description adds no additional parameter semantics beyond what the schema already documents.

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 function: 'Shut down the current browser and stop the meter.' This is a specific verb + resource combination that makes the core purpose obvious. It does not explicitly name sibling tools for differentiation, but the terminating nature is distinct enough from the listed siblings.

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 clear usage context: 'Read what you need first' signals that this should be called after data extraction is complete. It also notes the persistence caveat ('A profile is saved only when persistence was requested'), which informs the user whether they can expect preserved state. It does not explicitly contrast with alternatives like handoff or replay, but the when-to-use guidance is clear.

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