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

Annotations already declare the safety profile (not read-only, not idempotent, not destructive), so the description's job is to add context — and it does: it discloses the re-render/re-apply mechanics and that operations are created that can be watched via list_recent_executions. It does not say whether the call blocks or returns immediately, or what permissions are needed.

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, front-loaded with the action, followed by why it matters and how to observe the result. No filler or restatement of the name.

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 mutating, non-idempotent cluster-wide operation with no output schema, the description covers what changes, why, and how to track the resulting operations — a strong package. It omits timing/blocking behavior and scope of blast radius, which a fully complete definition would state.

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% and the single optional cluster_id already documents UUID format and the cluster-bound-conversation omission. The description refers only implicitly to "the cluster" and adds no syntax or defaulting detail beyond the schema, so 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 (reconcile) and resource (cluster) and explains the mechanism concretely: stack members re-render against committed definitions and variables, and drifted resources are re-applied. It does not, however, differentiate itself from nearby siblings such as reconcile_application, apply_stack_changes, or redeploy_stack, leaving the agent to infer the boundary.

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?

"This is how a variable change or an out-of-band edit converges" gives a clear trigger condition for reaching for this tool. There is no explicit when-not or named alternative (e.g., versus deploy/redeploy paths), so it stops short of full routing guidance.

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