pressable_reset_sftp_user_password

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

With no annotations, the description carries the full burden of disclosing behavioral effects. It fails to mention that this is a mutating action with security implications, whether the new password is returned (since no password parameter exists in the schema), what happens to the old password, or any permission requirements. The bare 'reset' provides no insight into consequences or response behavior.

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 no wasted words. It states the action and resource directly, earning its place without any fluff or redundancy.

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?

Given the lack of annotations and output schema, the description is insufficient for an agent to fully understand invocation. It does not specify what the tool returns (likely the new password), the necessity of site_id, or any side effects. The description is too short to cover the operational context for a sensitive mutation 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 0%, so the description must compensate for the parameters. While 'specific SFTP user' clarifies that 'username' identifies an SFTP user, it does not explain the role of 'site_id' or that the username is scoped to a site. The description adds minimal meaning beyond the parameter names and types.

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 uses a specific verb 'reset' with a clear resource: 'the password for a specific SFTP user.' It clearly distinguishes from sibling tools like pressable_get_sftp_users (listing users) and pressable_reset_wp_admin_password (resetting WordPress admin passwords), 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 guidance is provided on when to use this tool versus alternatives, nor are any prerequisites mentioned (e.g., the user must already exist, or how to obtain the username via pressable_get_sftp_users). The description merely states the action, leaving the agent to infer context entirely from the tool name and purpose.

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