octobrowser_delete_profiles

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

With no annotations, the description alone must convey behavioral expectations. It fails to mention that deletion is likely permanent, whether running profiles are affected, or if any confirmation or cleanup is involved. This is a critical omission 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, grammatical sentence that gets straight to the point. There is zero redundancy or filler, and the key action is front-loaded.

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 one-parameter tool, the description covers the essential purpose and parameter. However, the lack of annotations and absence of any safety context (permanence, impact on running profiles) leaves the description incomplete for a destructive action, though the low complexity keeps it from being severely deficient.

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 input schema fully documents the 'uuids' parameter with 100% coverage, so the description need not explain the parameter format. However, the description also adds no extra semantics beyond what the schema already provides, warranting the baseline score.

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 tool's function with a specific verb 'delete' and resource 'OctoBrowser profiles', and the 'one or more' wording accurately reflects the array parameter. This distinguishes it from sibling deletion tools for tags and proxies.

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 provides no explicit guidance on when to use this tool versus alternatives like octobrowser_delete_tag or octobrowser_delete_proxy. Usage is only implied by the tool name, and there are no exclusions or prerequisites mentioned.

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