browser_close

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

With no annotations, the description carries the full burden and falls short: it does not say whether the browser process is terminated, whether tabs/state/cookies are discarded, whether the operation is irreversible, or what happens if no session exists. 'Close' alone is the weakest possible disclosure for a destructive-ish lifecycle operation.

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?

A single front-loaded sentence with no filler; the scoping qualifier is placed immediately after the verb. It is efficient, though its brevity shades into under-specification rather than model concision.

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 zero-arg session-lifecycle mutation with no annotations and no output schema, the description should state at minimum what gets destroyed and whether the call is idempotent/safe when no session is open. None of that is present, so the agent goes in blind.

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 takes zero parameters, so per the baseline there is nothing for the description to compensate for. The one nuance worth stating — that it targets only this server's own session — is in fact present.

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 verb+resource ('Close the session') is identifiable, and 'owned by this server' adds a scoping nuance. But with siblings browser_close_window and browser_cleanup_session present, the description does nothing to disambiguate which 'closing' concept this is, leaving the agent to infer session-vs-window-vs-cleanup.

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?

No statement of when to call this rather than browser_close_window or browser_cleanup_session, and no prerequisites (e.g. must a session be open first?). Usage is only implied by the name.

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