Permanently delete

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

Annotations already set destructiveHint=true, but the description adds crucial context: 'This cannot be undone' and 'Only affects profiles already in trash'. This goes beyond the annotation by warning of irreversibility and preventing misuse outside the trash scope, providing robust behavioral transparency.

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 with no filler. The first sentence front-loads the action and scope, and the second adds irreversibility and a scope constraint. Every word earns its place.

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 tool with only two optional parameters and no output schema, the description covers all essential aspects: purpose, modes, irreversibility, and scope. A minor gap is the lack of explicit behavior when both all=true and profile_uuids are provided, but the implied exclusivity mitigates this.

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%, so baseline is 3. The description adds semantic value by explaining the two modes (specific via profile_uuids, bulk via all=true) and implying they are alternatives, which the schema does not enforce. This clarifies the relationship between the two parameters beyond their raw descriptions.

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 starts with an emphatic 'PERMANENTLY delete profiles from trash', which clearly states the action, resource, and scope. It also distinguishes from sibling tools like delete_profile (which likely moves to trash) and restore_from_trash by emphasizing irreversibility and the trash-only scope.

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 implies when to use this tool: when you want to permanently erase profiles already in trash, as opposed to initial deletion or restoration. It provides clear prerequisites ('Only affects profiles already in trash') and two usage modes, but does not explicitly name alternatives or exclusions beyond that.

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