List SFTP Users

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds the nuance that it lists 'additional' accounts, which clarifies scope. It does not disclose return format or any side effects, but for a read-only list with strong annotations, this is acceptable baseline.

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, front-loaded sentence with zero filler. It conveys the action, resource, and scope efficiently, earning its place.

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 one-parameter read-only list with no output schema, the description is adequate but does not specify the return format or any caveats about the response. Since there is no output schema, a brief note on what is returned would improve completeness, but it's not critical for such a straightforward operation.

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 100% for the single parameter (env_id), so the schema fully documents it. The description does not add any parameter-level details beyond what the schema provides, so the baseline of 3 applies.

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 clear verb ('List') and resource ('additional SFTP/SSH user accounts') scoped to an environment. Among siblings like kinsta_sftp-users_add, remove, and toggle, this is unambiguously the read operation. The word 'additional' also distinguishes it from the primary/default SFTP user, adding precision.

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 verb 'List' implicitly signals this is for viewing, not modifying, so usage context is implied. However, the description does not explicitly mention alternatives (e.g., use add/remove for changes) or state when-not-to-use it, leaving the routing to the agent's inference.

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