clusters_restart

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's claim 'Restart a running cluster' is consistent but adds no extra behavioral context. It does not explain side effects like interrupting running jobs or requiring permissions, which are already partially covered by annotations.

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 sentence, front-loaded with the core action. It is concise and free of fluff, though it could benefit from additional context without being verbose. Given the minimalism, it earns a high score for efficiency.

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 an output schema present and annotations covering destructiveness, the description provides the minimum viable information. However, it lacks context about the restart process, impact on running jobs, and prerequisites (e.g., cluster must be running). For a destructive action, more completeness would be helpful.

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 50% (only cluster_id has a description). The tool description does not add meaning beyond the schema for either parameter; restart_user is left undocumented both in schema and description. The description should compensate for the missing restart_user explanation but fails to do so.

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 'Restart a running cluster' uses a specific verb ('restart') and resource ('cluster'), clearly distinguishing it from sibling tools like clusters_start (for starting a stopped cluster) and clusters_terminate (for stopping). The purpose is 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?

The description provides no guidance on when to use this tool versus alternatives such as clusters_start, clusters_terminate, or clusters_resize. It does not specify prerequisites (e.g., cluster must be running) or mention situations where restart is appropriate.

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