Change SSH Password Expiration

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

Annotations include openWorldHint: true, but the description does not clarify any side effects or additional behaviors. It does not disclose whether changes are immediate, reversible, or require specific permissions. No contradictions with annotations, but the description adds no value beyond what annotations already hint at.

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 superfluous words. It is efficient and front-loaded with the main action. However, it could be slightly more informative without sacrificing brevity.

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?

The description is adequate but minimal. Given the presence of an output schema and fully described parameters, the description provides the essential purpose. Yet, it lacks any mention of typical values or consequences, so it is not highly complete.

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 has 100% description coverage for both parameters (env_id and exp_interval), so the description does not need to add extra meaning. However, it offers no additional context such as default values or format expectations, keeping it at baseline 3.

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?

Description clearly states the action (change), resource (SSH password expiration interval), and scope (for an environment). It effectively distinguishes from sibling tools like password or generate-password, which deal with the password itself rather than its expiration. The verb 'change' is specific and matches the expected mutation.

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 versus alternatives like kinsta.environments.ssh.password or kinsta.environments.ssh.generate-password. There is no mention of prerequisites, limitations, or typical scenarios. The description is a single sentence without any usage context.

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