Close Session

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

The annotation already declares destructiveHint=true, and the description adds the behavioral detail that it 'cleans up resources,' which goes slightly beyond the annotation. However, it does not disclose what specific resources are cleaned or that the session becomes invalid after this call. This is adequate but not rich given the destructive nature.

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, well-structured sentence of ten words. It is front-loaded with the primary action and resource, and every word adds meaning. No filler or redundancy exists.

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-parameter tool with a destructive annotation and an output schema, the description covers the essential purpose (closing the session) and behavioral detail (cleaning up). The output schema can handle return values, and the annotation covers destructiveness. The description is complete for this simple tool.

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 has zero parameters, and the input schema is empty, so schema coverage is trivially 100%. With no parameters to describe, the description does not need to add parameter semantics, and the baseline of 4 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 clearly states the action ('Close') and the resource ('the current browser session'), plus an additional consequence ('clean up resources'). This unambiguously distinguishes it from all sibling tools, which are about profiles, searches, messaging, and feeds, not session management.

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 usage (close the session when done), but does not explicitly state when to call this tool versus alternatives, nor does it provide any exclusions or prerequisites. Since there are no sibling tools for session management, the intended use is obvious, but the guidance is only implied, not stated.

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