delete_file

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete' implies destructive action, but the description does not mention whether the file is permanently deleted (vs. moved to trash), what happens on error (non-existent path, permissions), or if it can be undone. A simple warning about irreversibility would improve 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?

The description is extremely concise with one sentence and zero waste. 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?

Given the tool has 1 parameter, full schema coverage, and an output schema (likely indicating success/failure), the description could add more context about return value or error handling. It is minimally adequate but lacks behavior details for a destructive operation.

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% (path described in schema). The description adds no extra meaning beyond what's in the schema. Baseline 3 is appropriate because schema already documents the parameter well.

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 'Delete a single file.' uses a clear verb (delete) and specific resource (single file). It distinguishes from sibling 'delete_folder' and other file operations like 'move_file' or 'copy_file'.

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 usage for deleting individual files, but provides no guidance on when not to use it (e.g., instead of 'run_command' rm or other batch deletion), no prerequisites (file must exist), and no alternatives mentioned.

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