Delete browser profiles

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

Discloses nuanced deletion behavior: paid plans default to moving to the Basket, forceDelete makes it permanent, and Free plans require forceDelete. This goes beyond the annotations' destructiveHint and adds significant context about reversibility.

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 tightly written sentences, front-loaded with the core purpose followed by key conditions. No redundant wording or 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?

With no output schema and moderate complexity, the description covers the critical behaviors (Basket, forceDelete, password constraint) and the annotations cover safety. It might have mentioned prerequisites like stopping running profiles, but overall it is sufficiently complete.

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 schema only documents forceDelete, leaving ids and browserProfilePassword undescribed. The description compensates by explaining the 'one or more' semantic for ids and the password constraint, plus reinforcing forceDelete's permanence and plan requirement.

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 opens with 'Delete one or more profiles,' using a specific verb and resource that clearly distinguishes it from sibling delete tools like delete_proxy or delete_folder. It also clarifies the plural nature of the operation.

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?

Provides clear conditional guidance: forceDelete is mandatory on Free plans, and browserProfilePassword is only accepted for a single password-protected profile. However, it does not explicitly compare with alternatives, so it falls short of a 5.

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