ftp_delete

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

No annotations are provided, so the description must carry the full burden. It only states that the tool deletes a file, which is a destructive operation, but does not disclose irreversibility, error behavior, or permission requirements. The description adds little beyond the schema.

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 a single, front-loaded sentence that conveys the essential purpose without any wasted words. Every word contributes to understanding the tool's function.

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?

While the tool is simple (one parameter), the description omits critical context for a destructive operation: no mention of prerequisites, return values, error cases, or behavioral nuances. With no annotations and no output schema, the description leaves significant gaps for an agent to infer safe and correct usage.

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?

The schema already provides a description for the sole parameter 'path' ('Remote path on the FTP server'), achieving 100% schema_description_coverage. The tool description adds no additional semantic detail beyond labeling the target as a 'file', which is the baseline for high coverage.

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 action ('Delete') and the object ('a file on FTP server'), which distinguishes it from the sibling tool ftp_rmdir (used for deleting directories). This is a specific verb+resource combination.

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 no guidance on when to use this tool versus alternatives like ftp_rmdir or ftp_rename. It does not mention prerequisites (e.g., an active FTP connection) or edge cases (e.g., cannot delete directories).

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