ListCloudFormationStacks

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

With no annotations, the description must carry the behavioral burden. It usefully discloses scope ('current AWS account and region') and the return type, which is more than nothing, but it omits pagination behavior (important for listing 'all' stacks), permission requirements, and whether results are truncated.

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?

Short and front-loaded, with the core action stated first. There is minor redundancy between 'Retrieve all AWS CloudFormation Stacks' and 'lists all CloudFormation stacks in the current AWS account and region,' plus a near-vacuous return line, but nothing seriously wasteful.

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 zero-parameter, no-annotation list tool with no output schema, the description supplies the essential context: what it returns and where it operates. The main omission is pagination/'all' semantics, which is a modest gap given the tool's simplicity.

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 tool takes zero parameters, so the baseline is 4. There are no parameter semantics to clarify, and the description correctly does not invent any.

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 states a specific verb and resource ('Retrieve all AWS CloudFormation Stacks') and scopes it to the current AWS account and region. It is clearly distinguishable from siblings like GetStackResources or ListFISExperiments, though it does not explicitly name a sibling to differentiate against.

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?

Usage is only implied via the motivating clause 'providing information that can help identify potential targets for fault injection,' which hints at reconnaissance-style use. There is no explicit when-to-use guidance, no when-not-to-use, and no routing to alternatives such as GetStackResources for stack details.

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