scale_deployment

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

Discloses that it is a write operation recorded in audit log, and explains the effect on pods. Without annotations, the description adequately covers behavioral traits, though missing details on potential disruptions or permissions.

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?

Well-structured with a clear purpose statement, explanatory sentences, and an Args list. All sentences add value; could be slightly more concise but very reasonable.

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?

Covers input parameters thoroughly and provides usage guidance. Missing the return value/output description; given no output schema, the agent might wonder what the tool returns after scaling.

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 has 0% description coverage, but the description's Args section fully explains all 5 parameters, including nuances like gateway_id disambiguation and replicas meaning (suspend/run).

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?

Clearly states 'Scale the replica count of a Kubernetes deployment' with specific verb and resource. Distinguishes from sibling tools like run_kubectl or helm_upgrade by being specific to scaling replicas.

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 clear context: changes number of pods without adding nodes, and gives examples (0 to suspend, 1+ to run). However, does not explicitly compare with alternatives or state when not to use.

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