pressable_reset_sftp_user_password

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

With no annotations provided, the description carries full burden but fails to disclose critical behavioral traits: whether the old password is immediately invalidated, whether a new random password is generated, what the tool returns (likely the new password), or security implications. 'Reset' implies mutation but specifics are absent.

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?

Single sentence of seven words is efficient and front-loaded with the action. No redundancy, though extreme brevity contributes to information gaps in other dimensions.

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 security-sensitive password reset operation with no annotations, no output schema, and 0% parameter documentation, the description is inadequate. It should explain the return value (critical for a reset operation), parameter sources, and side effects, but provides only the basic action statement.

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 0% (neither site_id nor username have descriptions). The description mentions 'specific SFTP user' which loosely implies the username parameter, but completely fails to explain site_id, expected formats, or where to obtain these values (e.g., from `pressable_get_sftp_users`).

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 (reset), resource (password), and target (specific SFTP user). It distinguishes from sibling `pressable_reset_wp_admin_password` by specifying 'SFTP user'. However, it doesn't clarify what 'reset' means (random generation vs. custom setting).

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?

Provides no guidance on when to use this tool versus alternatives, prerequisites (e.g., needing to obtain valid site_id/username first), or when-not-use scenarios. No mention of required permissions or verification steps.

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