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

Annotations already mark destructiveHint=true, and the description adds the behavioral detail that pausing scales to zero running instances and is a mutating operation. This gives an agent more context than the annotation alone, though it does not discuss reversibility or side effects; still, the added context is meaningful.

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 that front-loads the mutating nature, states the action, and includes the endpoint. Every word earns its place with no redundancy or filler.

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 two-parameter tool with no output schema and no nested objects, the description is sufficient. It communicates the operation, the effect, and the HTTP method, and the annotations cover the destructive flag. Nothing an agent needs to invoke it correctly is missing.

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%: both projectId and serviceId have simple descriptions ('Project id.', 'Service id.'). The tool description adds no extra semantics for these parameters. Per the calibration baseline, a 3 is appropriate when the schema already documents all 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 states a specific verb ('pause') and resource ('service'), and adds a precise effect ('scaling it to zero running instances'). This clearly distinguishes it from sibling tools like resume, restart, or scale, and the HTTP endpoint provides additional unambiguous context.

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 action is clearly defined, and the name/description make it obvious when to call it. However, it does not explicitly mention that resume_service is the counterpart or call out scenarios where an alternative (e.g., scale_service to zero) could be used instead, so it misses the highest bar for explicit guidance.

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