session_close

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

Annotations provide no destructive hint, so the description carries the burden of behavioral disclosure. It states that resources are freed, which implies a state change, but it does not disclose consequences such as the session becoming invalid, in-flight navigations being aborted, or the irreversible nature of the close 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?

The description is a single concise sentence that front-loads the core action. Every word contributes to the meaning, with no filler or redundant information.

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 low complexity and a fully documented schema, the description covers the basic operation. However, it lacks behavioral context around side effects and usage preconditions, which is important for a closing/destructive operation, so the definition is adequate but not fully complete.

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 only parameter, session_id, has a clear description ('Session ID'). The tool description adds no further parameter-specific meaning, which is acceptable because the schema already fully documents the parameter.

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 action ('Close'), the resource ('a browser session'), and the purpose ('free its resources'). It is immediately distinguishable from sibling tools like session_create and session_list, which have opposite or different purposes.

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 implies when to use the tool: when a browser session should be closed and its resources freed. However, it does not explicitly state when not to use it or mention any alternatives, such as session_list or session_state for checking session status before closing.

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