AWS MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information beyond the implied read-only nature of 'Get'. It fails to specify the return format (JSON vs YAML string), potential error states for non-existent stacks, rate limiting considerations, or whether the operation incurs AWS API costs.

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 single-sentence description efficiently conveys the core purpose without redundant words or filler content, placing the essential action and resource at the beginning. However, its extreme brevity borders on under-specification given the complete absence of supplementary metadata.

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?

Considering the tool lacks annotations and output schema, the description should disclose the return value format, authentication context, or behavioral constraints regarding the `Original` vs `Processed` template stages. As provided, it leaves significant operational gaps for an AWS API tool with credential override parameters.

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?

While the phrase 'for a stack' implicitly references the required `stack_name` parameter, the description adds no semantic context for the optional `profile`, `region`, or `template_stage` parameters. Given 100% schema description coverage where all parameters are already well-documented, the baseline score of 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?

The description uses the specific verb 'Get' and identifies the target resource as 'CloudFormation template body', clearly indicating it retrieves the template definition for a stack. While it does not explicitly contrast with sibling tools like `aws_cfn_describe_stacks`, the specificity of 'template body' inherently distinguishes it from operations that return stack metadata or resource lists.

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?

The description provides no guidance on when to use this tool versus alternatives such as `aws_cfn_describe_stacks`, nor does it mention prerequisites like stack existence requirements or necessary IAM permissions. There is no discussion of when-not-to-use, failure modes, or explicit comparison to the four sibling CloudFormation tools.

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