delete_file

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

Discloses destructive, permanent nature, non-idempotence (throw on unknown ID), and file type-specific handling. No annotations provided, so description fully covers behavioral traits.

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?

Concise yet comprehensive: opens with 'DESTRUCTIVE', covers key behaviors, return value, and edge cases in a few sentences. No superfluous words.

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?

Thoroughly explains when to use, what it does, how it behaves for different file types, return format, and alternatives. With one parameter and no output schema, the description is highly complete.

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?

Only one parameter 'id' with schema description 'File ID'. Description adds minimal extra info beyond the schema, which already covers the parameter. Schema coverage is 100%, baseline 3 is appropriate.

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?

Clearly states the tool destructively deletes a file by ID, explains different behavior for KB files vs project reference files, and distinguishes from siblings like remove_tags, set_favorite, and bulk delete_files.

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?

Explicitly instructs to use only when the file is truly obsolete and provides alternatives (untag or unfavorite) to deprioritize without data loss. Also mentions a bulk variant.

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