aws_cloudformation

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

No annotations are provided, so the description carries full burden. 'Manage' implies both read and write operations, but the description doesn't disclose behavioral traits like required AWS permissions, potential destructive actions (create/update/delete), rate limits, error handling, or what 'manage' specifically entails. It leaves critical behavioral aspects unspecified.

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 extremely concise with just three words, front-loaded with the key information. There's zero waste or redundancy, making it easy to parse quickly.

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?

Given the tool's complexity (8 parameters, multiple actions including destructive operations, no annotations, no output schema), the description is incomplete. It doesn't address what the tool returns, error conditions, authentication requirements, or how different actions affect behavior. For a multi-action AWS management tool, this minimal description is inadequate.

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 0%, so the description must compensate but adds no parameter information. It doesn't explain what parameters like 'action', 'templateBody', 'capabilities', or 'parameters' mean, their formats, or how they interact. With 8 parameters and no schema descriptions, this is a significant gap.

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 'Manage AWS CloudFormation stacks' states the general purpose but is vague about what 'manage' entails. It specifies the resource (AWS CloudFormation stacks) but lacks a specific verb beyond the generic 'manage'. It distinguishes from siblings by focusing on CloudFormation rather than other AWS services, but doesn't clarify what specific operations are included.

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?

No guidance is provided on when to use this tool versus alternatives like terraform or other AWS tools (aws_ec2, aws_lambda, etc.). The description doesn't mention prerequisites, appropriate contexts, or exclusions. Users must infer usage from the action parameter alone.

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