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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds a non-obvious guardrail the annotations cannot express: ArgoCD-managed resources are rejected by default. It doesn't disclose apply semantics (create vs. server-side apply/patch), so it stops short of 5.

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?

Three sentences, zero filler, and the core action is front-loaded before the routing and safety caveats. Every sentence carries distinct 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 destructive write tool with no output schema, the description covers purpose, scope, routing and the key safety gate; what's left out is the return/outcome shape and whether a rejected call surfaces an error or a pending confirmation. Minor gap for an otherwise complete definition.

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%, so all five parameters (including allow_bypass and its warning) are already documented in the schema. The description only restates the manifest type and the bypass condition, adding no syntax or format detail beyond it — baseline 3.

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?

States a specific verb and resource ('Apply a Kubernetes manifest (YAML) to create or update resources') and scopes it ('Supports any Kubernetes resource type'), which separates it from validate_cluster_manifest, apply_cluster_manifest, patch_resource and the draft tools without opening any schema.

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 names the preferred path for stack-managed resources (add_manifest_to_draft + apply_stack_changes) and states the hard exclusion: direct apply against ArgoCD-managed resources is rejected unless allow_bypass=true. Both the alternative and the condition selecting it are given.

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