session_close

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

The description discloses a valuable behavioral trait: it stops Chrome while preserving the profile directory, which is not evident from the tool name or schema. With no annotations provided, this adds transparency beyond the basic action. However, it omits other potential behaviors such as lease token handling or effects on session state.

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, short sentence that communicates the core action and the key preservation caveat. It is front-loaded and free of filler. It misses the opportunity to add de-emphasized sibling context, but for a tool this small it is appropriately concise.

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?

The description is minimally sufficient for a simple close/session utility with three documented optional parameters and no output schema. It confirms the primary behavior and a key safety property. However, it would benefit from a note about interaction with leased sessions or the fact that the browser is stopped, and no alternative assignment is provided.

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 schema provides clear descriptions for all three parameters, including session selection and lease hints. The tool description itself does not add parameter semantics, but it is not required when the schema already fully documents them. Baseline 3 is appropriate.

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 uses the specific verb 'Stop' with the resource 'Chrome' and the scope 'for one session', which clearly identifies the tool's action. The parenthetical 'profile dir preserved' adds important scope distinction. It does not explicitly contrast with sibling tools like 'stop' or 'session_close_all', but 'for one session' provides enough differentiation.

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 guidance on when to use this tool versus its siblings. The description does not mention scenarios for using session_close instead of 'stop' or 'session_close_all', and no exclusions or prerequisites are provided.

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