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

Annotations establish mutate, non-idempotent, non-destructive, but the description adds material behavior the annotations cannot: two refusal conditions, a GitOps repository push side effect, and the fact that the change is reversible by renaming back. Auth requirements and exact failure messaging are still unspecified, so it falls just short of a 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?

Four short sentences, front-loaded with the core action, then preconditions, side effects, and reversibility. Every sentence carries distinct information with no repetition of the name or schema.

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?

With no output schema and full schema coverage, the description covers what an agent needs to decide and call: what is renamed, when it will be refused, the GitOps side effect, and reversibility. Only the return value or confirmation shape is left implicit, which is a minor gap.

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 three parameters (stack_name, new_name, cluster_id) are already documented in the schema, including the naming constraint and how to discover cluster ids. The description adds no further parameter-level detail, so the baseline 3 applies.

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 (Rename) and resource (a deployed stack on the cluster), which cleanly separates it from siblings like clone_stack, update_stack, and delete_stack. The scope 'deployed stack on the cluster' tells the agent exactly what object is targeted.

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 supplies precondition context (refused while pending drafts exist, or when the new name is taken), which implicitly tells the agent when the call will succeed. However, it never contrasts itself with alternatives such as update_stack or clone_stack, so alternative selection is left to inference.

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