create_deployment

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

No annotations are provided, so the description carries full burden. It only states 'Creates a new Deployment' without disclosing behavioral traits like dry-run support, permissions needed, or what happens on conflict. The dryRun parameter exists in schema but is not highlighted.

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, front-loaded, no wasted words. Every sentence serves a purpose.

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?

The description explains the two modes but lacks completeness for a creation tool. It doesn't mention that the namespace must exist, default values (e.g., dryRun defaults to true), or whether the tool can update existing deployments. Given the complexity (8 parameters), more context would help.

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 description coverage is 100%, baseline 3. The description adds meaning by explaining the two usage modes (basic config vs YAML manifest), which clarifies the role of parameters like port, image, replicas vs yamlManifest. This adds value beyond individual parameter descriptions.

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 tool creates a new Deployment, with specific verb+resource. It distinguishes from sibling tools like delete_deployment and scale_deployment by focusing on creation. The mention of two config methods provides clarity.

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 guidance on using basic configuration vs YAML manifest, but does not explicitly state when to use this tool over siblings (e.g., when to create vs update) or exclude misuse. No alternatives or prerequisites mentioned.

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