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

Annotations already declare readOnlyHint=true and the description reinforces this with 'Read-only'. Beyond that, the 'same export the cluster's IaC view serves' line adds useful provenance about the output. It does not describe size limits, whether the YAML is multi-document, or auth requirements, so it adds moderate value on top of the annotation.

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 short sentences, zero filler, with the core action and output format front-loaded and the usage cases following. Every clause earns its place.

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 one-parameter read-only tool with no output schema, the description covers purpose, output artifact, use cases, and the safety profile. The only meaningful gap is the lack of explicit differentiation from export_stack_profile_iac; the return format is adequately implied by 'YAML document'.

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?

With 100% schema description coverage on the single cluster_id parameter (including UUID format and a discovery hint pointing at list_clusters), the schema carries the full parameter burden. The description adds no parameter 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?

Names a specific verb (export) and resource (the cluster's stacks as an IaC YAML document), and distinguishes itself from the closely-named sibling export_stack_profile_iac by scoping to the cluster rather than a stack profile. The parenthetical clarifies it produces the exact artifact the cluster's IaC view serves.

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 states three use cases (show, back up, migrate the declarative configuration), which gives the agent clear context for when to reach for it. It does not, however, name or exclude the sibling export_stack_profile_iac, so the boundary between the two export tools 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.