close_session

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

Annotations include destructiveHint:true, and the description adds that it 'free resources' and explains the automatic reopening behavior. This goes beyond annotations by detailing what gets destroyed and the recovery mechanism, with no contradiction.

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 just two sentences, highly concise, and front-loaded with the core action. Every sentence serves a purpose without excess.

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 no parameters and the presence of an output schema, the description fully covers the tool's purpose, its usage context, and the automatic reopening behavior. It is complete for an AI agent to invoke correctly.

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 no parameters, so the schema provides no details. The description does not need to add parameter semantics, and with zero parameters, a baseline score 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 verb 'Close' and the resource 'browser', making the tool's purpose unambiguous. It distinguishes from sibling tools like authenticate and get_missions, as none of them perform session closure.

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 explicitly says 'Call this when you're done with Malt tools' and notes that the browser will reopen automatically if needed. This provides clear when-to-use guidance and future behavior, helping the AI agent decide correctly.

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