delete_ftp_user

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. For a destructive, likely irreversible operation it says nothing about confirmation requirements, permission scope, or side effects such as removing home directories or active sessions.

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 phrase is front-loaded and free of padding, but at three words it is under-specified rather than genuinely concise. Brevity here comes at the cost of all operational detail.

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?

With one required parameter, no output schema, and no annotations, the definition is too thin for a destructive mutation tool. Nothing tells the agent how deletion is confirmed, what happens to the account's data, or what a successful result looks like.

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 single 'id' parameter is undocumented, so the description must compensate. It does not clarify whether 'id' is the FTP account ID or username, nor whether it can be obtained from list_ftp_users.

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 states a specific verb (Delete) and resource (FTP user), so an agent knows exactly what it does at a glance. It offers no differentiation from close siblings such as update_ftp_user or operate_ftp, but the core purpose is unambiguous.

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 when-to-use guidance, no prerequisite (e.g. whether the account must be disabled first), and no mention of alternatives such as update_ftp_user or operate_ftp. The agent must infer usage purely from the name.

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