Scale instance count

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

Annotations show readOnlyHint=false and destructiveHint=false; description adds the critical caveat about autoscaling overriding the scale value. No contradictions. Does not describe return value or side effects, but the autoscaling disclosure adds meaningful behavioral context beyond 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?

Two sentences with a link and API call reference. Front-loaded with purpose, then behavior. Every sentence earns its place; no redundant 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?

For a simple mutation tool with 2 required params and no output schema, the description covers purpose, behavior, and a key edge case (autoscaling). It does not describe return format or error handling, but the absence of output schema and the annotations reduce the burden. Slightly more detail on response could elevate completeness.

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%; only serviceId has a description. The description adds context for numInstances by linking it to 'fixed number of instances' but lacks explanation of serviceId format or constraints. While the link to scaling docs provides some reference, parameter semantics are only partially elaborated.

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 'scale' and the resource 'service instance count'. It distinguishes from sibling tools like render_autoscale_service (which configures autoscaling) and render_get_instance_count (read-only). The inclusion of a documentation link and API call reinforces specificity.

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?

Explicitly notes that scaling is ignored when autoscaling is enabled, providing a when-not-to-use condition. Strong context for manual vs. autoscaling. Could mention render_autoscale_service as an alternative for configuring autoscaling, but given sibling tool list, this is a minor gap.

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