Delete Duplicate Files

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

No contradiction: 'Permanently deletes' aligns with readOnlyHint=false and destructiveHint=true. Beyond the annotations it adds the safety detail that it 'Verifies hash/size before deletion' and stresses permanence — useful behavioral context for a destructive operation, since the annotations already carry the core destructive flag.

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 tight sentences with the DESTRUCTIVE warning front-loaded; no filler. Only minor deduction for not using the available lines to cover the undocumented parameters.

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 destructive tool with no output schema and 0% parameter coverage, this is thin. It never tells the agent that a backup manifest can be created (create_backup_manifest defaults true), whether deletion is recoverable via undo_last_operation, or what the response contains. An agent cannot fully predict the consequences of calling it.

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?

With 0% schema description coverage, the description must compensate, but it only vaguely references 'specified duplicate files' for the required files_to_delete array. Nothing explains path format, nor the behaviors of response_format or create_backup_manifest — what a backup manifest does is left entirely to inference.

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?

"Permanently deletes specified duplicate files" states an unambiguous verb (deletes) and resource (duplicate files) with a permanence qualifier. It clearly separates this from read-only siblings like find_duplicate_files and analyze_duplicates, which an agent can spot without opening schemas.

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 gives no guidance on when to use this tool versus alternatives. It never mentions the prerequisite flow (finding/analyzing duplicates first) nor the relationship to undo_last_operation or analyze_duplicates. The DESTRUCTIVE warning conveys caution but not usage conditions or exclusions.

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