browser_close

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is known from structured data. The description does add real value beyond that: it names the exact scope of destruction (tabs, cookies, storage) and carves out an exception that profile sessions retain saved logins on disk. It says nothing about what happens if the session id is unknown or already closed.

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?

Two short sentences with zero filler; the destruction scope is front-loaded and the profile-login caveat follows as a qualifier. Every clause earns its place.

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 one-parameter destructive tool with no output schema, the description covers the important behavioral question (what is lost, what survives). The remaining gap is routing: nothing tells the agent how this relates to session_close, which is the most likely misuse path given the sibling list.

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 description coverage is 100% and the single 'session' parameter is documented in the schema as an isolated browser with a 'default' fallback. The description adds no meaning about the parameter, which is the correct baseline when the schema carries the burden.

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?

Specific verb (Close) plus resource (this session), with an enumeration of what is torn down: tabs, cookies, storage. It stops short of distinguishing itself from the near-identical sibling session_close, which an agent would reasonably confuse it with.

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?

There is no explicit statement of when to call this versus session_close, or versus simply leaving the session open. Usage is only implied by the verb 'Close'. The default-session behavior (no argument) is also not addressed.

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