delete-browser

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete the browser' implies a destructive mutation, but it doesn't specify permanence, side effects, permissions required, or error handling. This is inadequate for a tool with clear destructive potential.

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 ('Delete the browser') with zero wasted words, making it front-loaded and easy to parse. However, this brevity comes at the cost of completeness for a destructive operation.

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 destructive tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'delete' entails operationally, what happens to associated resources, or what the return value might be, leaving critical gaps for agent decision-making.

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?

Schema description coverage is 100%, with the parameter 'userIds' clearly documented as required user IDs for deletion. The description adds no additional parameter semantics beyond what the schema provides, meeting the baseline for high schema coverage.

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 'Delete the browser' states a clear verb ('Delete') and resource ('the browser'), but it's vague about scope and lacks differentiation from siblings like 'close-browser' or 'update-browser'. It doesn't specify whether this deletes browser instances, configurations, or user data.

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 guidance is provided on when to use this tool versus alternatives like 'close-browser' or 'update-browser'. The description doesn't mention prerequisites, exclusions, or contextual factors for choosing this deletion operation.

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