profile_delete

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

With no annotations supplied, the description must carry the full behavioral burden. It does disclose the destructive scope (profile plus macOS launchers) and the ordering guarantee that symlinks are unlinked first, which is real added value, but it says nothing about irreversibility, required permissions, or how the confirm/force_stop flags change behavior.

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?

A single front-loaded sentence with no filler; the destructive action is stated first and the safety ordering follows. The trailing 'safely' is slightly redundant but costs little.

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?

This is a destructive mutation tool with no annotations, no output schema, and zero parameter documentation, so the description should explain the confirm requirement and what force_stop does. Instead it covers only the high-level action and leaves the agent guessing about the two required/optional flags.

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 0% across three parameters, and the description never mentions name, confirm, or force_stop. The meaning of the mandatory confirm flag and the optional force_stop flag is left entirely unexplained, so the description adds nothing to the bare 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 names a specific verb and resource: delete a sandbox profile plus its macOS launchers. That is enough to tell it apart from profile_create, profile_clone, or launcher_remove by name alone, though it does not explicitly contrast itself with those siblings.

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?

It hints at a precondition ('after unlinking managed symlinks safely') but never states when an agent should choose this over profile_update or launcher_remove, nor what state the profile must be in before deletion. There are no exclusions or alternative-routing guidance.

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