ftp_delete

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

The description discloses that deletion is permanent ('Permanently remove') and includes a caution. However, with no annotations, it fails to mention other behavioral traits such as whether deletion is recursive, whether confirmation is required, or if there are authentication or permission implications.

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 only two short phrases. It front-loads the core action and adds a caution. No extraneous text, though it could be slightly more structured (e.g., separating purpose from warnings).

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?

For a simple one-parameter tool with no output schema, the description covers the essential purpose and behavior. However, given the many sibling tools, additional context about file scope (e.g., only files, not directories) or a reference to ftp_rmdir for directories 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?

Parameter schema coverage is 100%, and the description adds no significant meaning beyond the schema's own description ('The remote file path to be destroyed'). The tool description implies the path is a file path, but the schema already conveys this.

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 permanently removes a file from the remote server. The verb 'remove' and resource 'file' are specific, and it distinguishes from sibling tools like ftp_rmdir (removes directories) and ftp_list (lists 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?

The description provides no guidance on when to use this tool versus alternatives like ftp_rmdir or ftp_batch_upload. The only advisory is 'use with caution,' which is too vague for an AI agent to select the correct tool among many siblings.

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