camofox_destroy_session

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

With no annotations provided, the description carries the full burden. It discloses destructive behavior ('closes all tabs and cleans up state'), but lacks details such as whether the action is reversible, what happens to unsaved data, or if any confirmation is required. The description is functional but not thorough.

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 extremely concise: two sentences that convey the core action and its effects. No extraneous text. Front-loads the verb and resource immediately.

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 simple tool with one parameter and no output schema, the description covers the basic functionality. It explains what is destroyed (session, tabs, state) and identifies the required input. Minor gaps exist (e.g., return value, error conditions), but the description is adequate for typical use.

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 only parameter, userId, is mentioned in the description ('for the given userId'), but no additional context is given about its format, source, or implications. The schema coverage is 0%, so the description should compensate but does so minimally. The agent might not know how to obtain the correct userId.

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 'Destroy a user session' and elaborates with 'Closes all tabs and cleans up state for the given userId,' making the verb and resource explicit. It distinguishes from sibling tools like camofox_stop_browser (which stops the browser process) and camofox_cleanup_idle_tabs (which targets idle tabs rather than a full session).

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?

No explicit guidance on when to use this tool versus alternatives. The description does not mention prerequisites, typical scenarios, or when not to use it. For example, it does not contrast with camofox_stop_browser or explain if destroy_session is needed before or after other operations.

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