AWS MCP Server

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

No annotations provided, so description carries full burden. While 'Get' implies a read-only operation, the description omits critical behavioral context: AWS authentication requirements, potential costs, pagination behavior, or error conditions (e.g., stack not found).

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?

Single sentence, efficiently structured with the parenthetical adding specificity without verbosity. Every word earns its place, though 'detailed info' is slightly generic without the parenthetical clarification.

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?

No output schema exists, so return value documentation falls to the description. While it lists key data categories (parameters, outputs, tags), it lacks structure documentation (nested objects, arrays) or sample output. Acceptable but incomplete given the richness of CloudFormation stack data.

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 coverage, baseline is 3. The description adds value by clarifying the optional nature of stack_name via 'one or all', and the parenthetical explicitly lists what 'detailed info' encompasses (parameters, outputs, tags), providing semantic context not present in the schema.

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?

Excellent clarity: specific verb 'Get' + resource 'CloudFormation stacks' + scope 'one or all'. The parenthetical '(parameters, outputs, tags)' specifically distinguishes this from sibling aws_cfn_list_stacks (which returns summaries) and signals the detailed nature of the data returned.

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?

Lacks explicit guidance on when to use versus aws_cfn_list_stacks or aws_cfn_describe_stack_events. The phrase 'one or all' implies optional filtering behavior but does not constitute usage guidelines or prerequisites (e.g., AWS credentials).

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