scale_deployment

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

No annotations; description adds constraint '0..max' and 'allowlist' but does not explain side effects, idempotence, or what happens when replicas exceed max. Partial transparency.

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?

Single sentence, very concise, front-loads action. However, it omits parameter details and usage context, which could be included without adding length.

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?

Description is minimal for a 3-param tool with output schema. Does not cover return values, allowlist details, or behavioral aspects like immediacy or waiting. Incomplete given complexity.

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 0%; description does not explain any parameter individually. Only broad constraint on replicas is mentioned. No per-parameter guidance.

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?

Description states 'Scale a deployment to N replicas' with clear verb and resource. It distinguishes from siblings like restart_deployment and delete_pod by focusing on scaling replicas. The constraint '0..max' and 'allowlist' add 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?

No explicit guidance on when to use vs alternatives. Siblings include similar operations but description does not provide context or prerequisites.

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