set_cluster_scale

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

No annotations are provided, so the description carries the full burden. It discloses the required scope ('Requires scope services:write'), server-side constraints ('minimum >= 1 and maximum >= minimum'), and that it adjusts an existing pool. It could mention whether it overrides or merges with existing settings, but the action 'Set' implies override.

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 four sentences with no wasted words. It front-loads the action, then covers requirements, constraints, and differentiation from a sibling tool. Every sentence adds value.

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?

For a simple tool with three required parameters and no output schema, the description covers all necessary information: what it does, prerequisites, server-side constraints, and how it relates to other tools (list_services, get_cluster_scale, add_cluster_pool). It is complete for agent selection and invocation.

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 100%, so baseline is 3. The description adds context beyond the schema by explaining the purpose of each parameter in the tool's action: 'minimum' and 'maximum' are worker counts for the first pool, 'service_id' comes from list_services. It reinforces constraints already in schema but adds meaning in context.

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 clearly states the verb 'Set' and the resource 'autoscaling bounds (minimum/maximum worker count) of the FIRST node pool of a managed Kubernetes cluster.' It distinguishes from the sibling tool 'add_cluster_pool' by explicitly noting that it adjusts an existing pool rather than adding one.

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 explicit guidance on when to use this tool: 'Adjusts an existing pool — it does not add one (use add_cluster_pool for that).' It also specifies prerequisites: 'service_id comes from list_services' and how to read current sizing with 'get_cluster_scale'.

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