Add SFTP User

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

With only 'openWorldHint': true in annotations, the description carries the full burden for behavioral disclosure. It confirms a mutation ('add') but does not mention side effects, permissions required, limits on number of users, or any other behavioral traits. No contradiction with annotations.

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 sentence of 13 words, front-loaded with the key information. Every word is essential, and it is as concise as possible for the purpose.

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 create tool with an output schema present, the description is minimally adequate. However, it lacks details about constraints (e.g., username format, password rules) and does not address the 'openWorldHint' annotation, which might require more context for safe 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?

Schema coverage is 100%, with each parameter described adequately in the schema. The description adds no additional meaning beyond restating the action. Baseline of 3 is appropriate since the schema does the heavy lifting.

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 explicitly states 'Add a new additional SFTP/SSH user account to an environment,' clearly identifying the action (add), the resource (SFTP/SSH user account), and the scope (to an environment). This differentiates it from siblings like 'list', 'remove', and 'toggle'.

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, nor any prerequisites or context. It only states the action, leaving the agent to infer appropriate usage from the tool name.

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