delete_profile

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions permanent deletion of cookie data but is ambiguous about what else is deleted (e.g., history, bookmarks). Lacks details on side effects, authorization needs, or error conditions.

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?

Two sentences clearly state the action and permanence. No unnecessary words. However, it could be more informative without additional length, e.g., specifying what exactly is deleted.

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 required parameter and no output schema, the description is moderately complete. It covers the basic purpose and permanence but lacks details on error handling, prerequisites, and full scope of deletion (profile vs cookies only).

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% and already describes the profileId as 'Profile name to delete'. The description adds minimal value by repeating 'saved browser profile' but does not clarify naming conventions, existence requirements, or format validation beyond the 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) and the resource (saved browser profile), and it distinguishes from sibling tools like save_profile and load_profile by specifying permanence and disk removal.

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 or avoid this tool. It does not mention prerequisites (e.g., profile existence) or alternatives (e.g., other profile management tools). The description implies finality but no warning about cascading effects.

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