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

The annotations already flag destructiveHint=true, and the description adds valuable behavioral detail: the action is permanent and precisely scoped to the named slug, with no collateral removal. This goes beyond the raw annotation and helps an agent warn the user appropriately.

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 sentence that front-loads the destructive action, conveys permanence, gives examples, and ends with a precise scoping warning. There is no filler or redundant restatement of the title.

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, no-output-schema destructive tool, the description tells the agent what will happen, what can be targeted, and the key consequence (permanence). It is sufficient for an agent to select and invoke the tool correctly.

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 already documents 'slug' as the item to drop, so coverage is complete. The description enriches the parameter's meaning by clarifying that the slug identifies a specific owned item and by giving concrete examples of what kinds of items qualify, which helps the agent gather the right value.

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 uses a specific verb ('drop') and a clearly defined resource ('a specific owned item'), and it enumerates what kinds of items can be dropped: skill, look, persona, voice. This also distinguishes it from sibling tools like list_skills or reset_style by indicating this is a targeted, intentional 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?

It gives clear context for when to use the tool: when you regret a specific owned item and want to permanently get rid of it. It does not explicitly name alternatives or state when not to use it, but the targeted scope and 'only what you name goes' provide adequate selection guidance.

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