AWS MCP Server

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

With no annotations provided, description carries full disclosure burden. 'Purge' implies destructive deletion, and readonly constraint is documented. Missing: async behavior confirmation, IAM permission requirements, whether queue attributes/configuration persist after purge, or irreversibility warnings.

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?

Two sentences, zero waste. First sentence establishes purpose immediately; second sentence provides critical operational constraint. Appropriately sized for tool complexity.

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?

Adequate for a 3-parameter destructive operation with no output schema. Covers core action and readonly constraint. Could be strengthened with AWS-specific context (IAM permissions required, that queue metadata is preserved) given zero annotations.

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 100%, establishing baseline of 3. Description does not mention parameters explicitly, but schema adequately documents profile, region, and queue_url without needing elaboration in description text.

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?

Clear specific verb ('purge') + resource ('SQS queue') + scope ('all messages'). Distinct from siblings like aws_sqs_receive_message (retrieval) and aws_sqs_send_message (creation) through precise terminology.

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?

Provides operational constraint ('Blocked in --readonly mode'), indicating execution environment requirements. However, lacks explicit guidance on when to prefer purge over individual message deletion or receive+delete workflows.

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