Generate SSH Password

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

The description does not disclose effects like invalidating existing passwords, requiring authentication, or being irreversible. Annotations only have openWorldHint, which is vague. No contradiction.

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 with no redundancy. Efficient but could include more value (e.g., output or side effects) without losing conciseness.

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?

With one parameter, high schema coverage, and output schema available, the description is minimally adequate. Missing context about return value or behavioral effects.

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 covers 100% of parameters (env_id), and the description does not add additional meaning beyond the schema description. Baseline score 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 'Generate a new SSH/SFTP password for an environment.' uses a specific verb ('Generate') and resource (SSH/SFTP password for an environment), clearly distinguishing it from sibling tools like ssh.password or sftp-users.

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 on when to use this tool vs alternatives (e.g., ssh.password or sftp-users). Does not mention prerequisites, whether it resets vs creates, or when generation is appropriate.

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