clusters_resize

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

Description adds the precondition 'must be RUNNING', which is beyond annotations that declare readOnlyHint=false and destructiveHint=true. Useful context for safe invocation.

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?

Very short (5 words) but concise and includes a critical precondition. Could be structured better with bullet points, but it's adequate.

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 tool simplicity (2 params) and presence of output schema, the description is mostly adequate but fails to cover num_workers semantics.

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 50%; cluster_id has a description but num_workers lacks any description. The description does not add meaning to parameters.

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 'Resize a cluster (must be RUNNING)' clearly states the action (resize) and resource (cluster) with a precondition. It distinguishes from siblings like clusters_create, clusters_delete, clusters_edit, etc.

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 a clear precondition ('must be RUNNING') for using the tool. Does not explicitly mention when to avoid or use alternatives, but context is clear.

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