Close the browser

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

Goes well beyond the annotations by disclosing that the AnkiWeb session persists, that the next browser-needing call restarts it, and that an idle timeout closes it automatically. This is exactly the kind of side-effect and lifecycle context the readOnlyHint/idempotentHint flags cannot convey.

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?

Three short sentences, front-loaded with the action and purpose, then the state-persistence and auto-close caveats. Every sentence adds a distinct, useful fact with no filler.

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 no-arg lifecycle tool with annotations and an output schema, the description covers the essentials an agent needs: what it does, what survives, and that it self-restarts and self-closes. Nothing material is missing.

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 nothing for the description to clarify and no schema gap to compensate for. Baseline 4 applies; no parameter behavior is misstated.

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?

States a specific verb (Close) and resource (the server's headless browser) plus the motivation (free memory), which no sibling tool covers. An agent can immediately distinguish this lifecycle tool from the deck/session tools listed as siblings.

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?

Gives a clear timing condition ('once any call in progress has finished') and an implicit reason to call it (free memory). It also warns that the browser auto-closes after five idle minutes, which effectively tells the agent the call is often optional, but it never explicitly states when not to call or names an alternative.

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