get_stack_outputs

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

No annotations are provided, so the description carries the burden. It discloses that it reads local IaC files rather than the deployed stack, and details CDK stale-flag behavior with 'stale' and 'staleReason' fields, warning not to rely on stale exports. This goes beyond basic safety and informs the agent about freshness semantics.

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?

The description is three sentences, each with distinct value: results, usage, and stale-caveat. It is front-loaded with the primary purpose and avoids repetitive or irrelevant detail. No wasted words.

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?

Despite lacking an output schema or annotations, the description covers what is returned, when to use, when not to use, and a subtle behavioral detail about stale CDK outputs. This is sufficient for an agent to select and invoke the tool correctly.

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?

The schema has one parameter (maxAgeSeconds) with 100% coverage; the schema's own description fully explains its semantics, including advisory behavior and dataHealth reporting. The tool description does not add parameter-level details, but the schema covers it well, warranting the 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?

The description clearly states the tool returns stack outputs and cross-stack exports from local IaC files (Terraform and CloudFormation/CDK). It distinguishes itself from sibling tools by focusing on cross-stack export names and explicitly noting it does not return live resource attributes. The verb 'Returns' is specific and the resource scope is precise.

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?

It explicitly states when to call: when wiring cross-stack references (Fn::ImportValue, terraform_remote_state) or when needing the exported name of a resource in another stack. It also provides an exclusion: do NOT call for live resource attributes, as outputs come from local IaC files. This clear when/when-not guidance is exemplary.

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