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 fails to mention mutation safety, pagination limits, return format (queue URLs vs ARNs), or required IAM permissions. The single sentence provides only the basic operation type without operational context.

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 consists of a single efficient sentence that front-loads the primary action. However, given the tool's operational complexity (AWS service interaction with no output schema), the extreme brevity leaves significant informational gaps rather than demonstrating purposeful restraint.

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?

Lacking both an output schema and annotations, the description should explain what data is returned (queue URLs, ARNs, or metadata) and operational constraints like pagination. The minimal one-sentence description leaves critical gaps in the agent's understanding of the tool's complete behavior.

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 input schema has 100% description coverage, adequately documenting all three parameters without requiring description supplementation. The description mentions the 'optional name prefix filter' which aligns with the queue_name_prefix parameter but adds no semantic detail beyond the schema descriptions.

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 identifies the action ('List') and resource ('SQS queues') and mentions the filtering capability. However, it does not distinguish this list operation from the sibling aws_sqs_get_queue_attributes or indicate result scope (paginated vs complete).

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 mentions the 'optional name prefix filter' which hints at one usage pattern, but provides no explicit guidance on when to use this versus other SQS operations. There is no mention of pagination behavior, permission requirements, or prerequisites like AWS credentials.

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