Resume Cluster

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

Annotations declare readOnlyHint=false and destructiveHint=true, signaling a mutating operation. The description adds important context beyond annotations: that resuming is asynchronous, it returns the updated cluster, and that the RawTree API requires an organization admin token. These details help the agent understand side effects and required permissions.

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 well-structured with bolded sections (Purpose, Returns, Auth, Safety) and is front-loaded with the core action. It is slightly verbose in the Safety section, but each sentence contributes useful information.

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 complexity of a mutation tool and the lack of an output schema, the description covers the essential aspects: purpose, asynchronous behavior, return value, authorization requirements, and a safety warning. It is nearly complete, though it could mention error conditions or rate limits.

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 100%, so the input schema already fully documents the two parameters (organization and clusterId). The description does not add any new semantic details about parameter formatting or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific action (resume) for a specific resource (paused RawTree dedicated cluster), clearly distinguishing it from the sibling pause-cluster. It names the required precondition ('paused') so the agent knows the tool only applies to paused clusters.

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 explicitly says to use get-cluster to check progress after resuming, and implies the tool is for paused clusters. It does not explicitly state when NOT to use it (e.g., for running clusters) or list alternatives like pause-cluster, but the context is sufficiently clear from the 'paused' precondition.

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