roxy_delete_browsers

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

With no annotations, the description must disclose behavioral traits. It states 'permanently', implying irreversibility, but omits details on side effects (e.g., associated data deletion), authorization needs, error handling, or whether browsers must be closed first. The description is minimal and leaves significant gaps for a destructive 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?

The description is a single concise sentence with no filler. It front-loads the verb and resource, making the purpose immediately clear. Every word earns its place.

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 the lack of output schema and annotations, the description is incomplete. It does not explain return values, success/failure behavior, partial deletion possibilities, or rate limits. For a destructive tool, crucial context 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?

Schema coverage is 100%, providing baseline 3. The description adds context for dirIds ('by their directory IDs'), but does not clarify workspaceId usage or provide additional constraints/format beyond the schema. No extra value for a simple two-param schema.

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 action ('Delete'), the resource ('multiple browsers'), and the method ('by their directory IDs'). It distinguishes this from sibling tools like roxy_close_browsers (close vs delete) and roxy_delete_accounts (browsers vs accounts).

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 implies usage for permanently deleting multiple browsers by IDs, but provides no explicit guidance on when to use versus alternatives (e.g., roxy_close_browsers, roxy_delete_accounts) or when not to use (e.g., prerequisites like browser state). No exclusions or context are given.

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