ecp_files_delete

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

With no annotations, the description carries the burden of behavioral disclosure. It does state the critical fact that deletion is 'Irreversible,' which is essential for a destructive operation. However, it does not mention the required confirmation flag, whether folder deletion is recursive, or any permissions needed.

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 short sentences with no filler. The core action is front-loaded, and the critical warning 'Irreversible' is placed immediately after. 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?

The tool is simple and the schema is minimal, but with no annotations and no output schema, the description could do more. It omits the confirmation requirement and expected outcomes or errors, leaving some important context for an agent deciding whether to invoke 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?

Schema description coverage is 0%, and the description adds almost no parameter-level meaning. It implies file_path by saying 'file or folder' but does not explain the confirm parameter or its true-required semantics, which is a meaningful gap for a destructive operation.

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 uses a specific verb and resource: 'Delete a single file or folder.' It clearly scopes the operation to a single item, which differentiates it from the sibling ecp_files_delete_multiple and related file operations like rename or move. The purpose is immediately understandable.

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 phrase 'single file or folder' provides clear context for when this tool applies, but it does not explicitly name alternatives such as ecp_files_delete_multiple for batch deletions. It implies the boundary without stating when-not-to-use or exclusions explicitly.

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