ftp_delete

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

With no annotations, the description carries the full burden of behavioral disclosure. It hints at a confirmation requirement and impersonation, but 'confirm: Required' is vague and arguably conflicts with the schema, and there is no statement about irreversibility, permissions, or side effects.

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 short and front-loaded with the core action before the arg list. Each line is brief, though the misleading 'confirm: Required' line keeps it from being excellent.

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 destructive mutation with no annotations, the description omits how confirmation should be expressed, whether deletion is permanent, and what ownership or impersonation requirements mean in practice. The output schema may cover return values, but the operational context is incomplete.

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 0%, so the description must compensate. It adds small clarifications like 'FTP username' and 'Owning user,' but 'domain: Domain' is tautological and 'confirm: Required' is unclear and contradicts the schema's non-required status for confirm.

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 opens with 'Delete an FTP account,' a specific verb and resource that clearly distinguishes it from siblings like ftp_create and ftp_list. No ambiguity about what the tool does.

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?

There is no guidance on when to use this tool versus alternatives such as ftp_list or ftp_create, nor any prerequisites, exclusions, or conditions. The intended usage must be inferred entirely from the tool name and sibling list.

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