close_session

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

Without annotations, the description must carry the behavioral disclosure burden. It usefully reveals that sessions auto-expire and that closing frees resources, but it doesn't state whether closing is irreversible, whether invalid session IDs error, or what side effects occur beyond resource release.

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 concise sentences front-load the action and rationale, then add useful lifecycle context. No fluff or 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 single-parameter tool with no output schema, the description covers what, why, and when to call it, plus the session lifecycle context. It omits error/idempotency details but these are minor for a straightforward session-close operation.

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%, so the only parameter's meaning is already documented. The description adds no format, requirement, or default information beyond 'session ID to close'.

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?

States a clear action ('Close'), the resource ('a browser session'), and the rationale ('to free resources'). This distinguishes it from the sibling browse, which is about using/navigating a session rather than ending it.

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?

Explicitly advises that cleanup is recommended and informs the user that sessions auto-expire after 5 minutes, which tells when an explicit call is necessary. It doesn't discuss when not to use it, but for a simple cleanup tool this context is sufficient.

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