delete-file

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

With no annotations, the description carries the full burden. It discloses the destructive behavior ('Permanently delete') and the scope (namespace). However, it does not mention additional traits like irreversibility, authorization needs, or error conditions, which would enhance 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 two sentences, front-loaded with the main purpose, and uses no unnecessary words. Every sentence adds information: purpose, usage, and differentiation.

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?

The description is fairly complete for a delete operation with 3 parameters and 100% schema coverage. It includes scope, naming conventions, and sibling differentiation. However, it lacks information about return values or confirmation of deletion, which would improve completeness.

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%, providing a baseline of 3. The description adds value by explaining the snake_case naming convention and clarifying that at least one of file_name or file_names is required, which is not evident from the schema alone.

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 clearly states the tool's action: 'Permanently delete file(s) from document storage (S3) for a namespace.' It identifies the specific resource (file(s) in S3) and differentiates from the sibling tool 'delete-data' by clarifying that it deletes storage objects, not indexed documents.

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 provides explicit guidance on when to use this tool and when to use the alternative: 'This deletes storage objects, not indexed documents by pipeline ID (use delete-data for documents/vectors by id).' It also specifies the naming convention ('snake_case') and requirement ('At least one is required').

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