Toggle SFTP Users

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

The description provides a straightforward action, but lacks detail on behavioral traits such as whether existing SFTP sessions are affected, required permissions, or side effects. Annotations include openWorldHint, which suggests additional complexities, but the description does not elaborate. Given the tool's simplicity, the description is adequate but not thorough.

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, concise sentence that immediately conveys the purpose. It is front-loaded and contains no extraneous information. Every word adds value.

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 toggle tool with two parameters and an output schema, the description is nearly complete. It could be improved by clarifying what 'additional accounts' means and how this toggle interacts with existing individual SFTP users, but the current description is sufficient for basic understanding.

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?

The input schema has 100% description coverage for its two parameters (env_id and is_enabled). The description does not add any extra meaning beyond the schema definitions. Baseline score of 3 is appropriate since the schema already documents the parameters clearly.

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's action: 'Enable or disable additional SFTP/SSH accounts for an environment.' It includes the verb (enable/disable), resource (additional SFTP/SSH accounts), and scope (for an environment). This distinguishes it from sibling tools like add, list, and remove, which handle individual accounts.

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 does not provide explicit guidance on when to use this tool versus alternatives. It implies that it toggles the feature for additional accounts, but does not mention that individual account management should be done with kinsta.sftp-users.add/list/remove. Usage context is implied but not explicitly stated.

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