Close the browser

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the profile-state rule and the temporary-profile deletion case, but says nothing about what happens to open tabs, unsaved form data, in-flight navigation, or whether the result is reported back to the caller — significant gaps for a shutdown 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?

Two short sentences with the state-persistence consequence front-loaded after the core action; nothing is padded or restated from the name.

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 no output schema, the description covers the action and the most important side effect (profile retention vs deletion). Only the treatment of open tabs and any failure modes are left unaddressed.

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 takes zero parameters, so there is no schema meaning for the description to add; baseline applies and no parameter text is needed.

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 names a specific verb and resource ("Closes the browser cleanly") and adds a scope detail (profile persistence) that separates it from a mere tab operation. It never explicitly contrasts itself with the sibling tab_close, so an agent must infer that this ends the whole browser session rather than one tab.

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?

Usage is only implied: the mention of profile state suggests this is the end-of-session shutdown rather than a per-tab cleanup, but there is no explicit "use this when / use tab_close instead" statement or prerequisite guidance.

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