Add FTP user

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

With no annotations, the description must fully disclose behavior. It mentions KAS auto-generates the login prefix and warns about unverified parameters, but omits details on side effects, idempotency, authentication needs, or what happens if the user already exists.

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?

Extremely concise: two short sentences that front-load the core purpose and then provide a critical note. No wasted words.

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 description is incomplete for a creation tool with 3 parameters and no output schema. It fails to describe return values, error conditions, or any post-creation behavior. The warning about unverified params is helpful but does not compensate for missing output and usage context.

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 100% with basic descriptions. The tool's description adds value by noting the login prefix is auto-generated, but the warning that params are unverified introduces uncertainty, reducing reliability. Baseline of 3 is appropriate.

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 verb 'Create' and resource 'FTP user', and the parenthetical '(add_ftpusers)' directly ties to the tool's name. It distinguishes from siblings like ftp_delete and ftp_list, making the tool's purpose 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?

No explicit guidance on when to use this tool versus alternatives such as ftp_update or ftp_list. The description lacks prerequisites, exclusions, or context for choosing this tool over siblings.

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