sqs_purge_queue

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

With no annotations provided, the description carries the burden of disclosing behavior. 'Purge all messages' clearly indicates a destructive, bulk-removal action, and adding 'in LocalStack' provides a contextual constraint. Though it doesn't explicitly state irreversibility, 'purge' strongly implies permanence, and the simplicity of the operation makes this sufficient.

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 a single, front-loaded sentence with no extraneous content. Every word contributes to explaining the tool's purpose.

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?

For a tool with one parameter, no output schema, and a clear action, the description is complete. It states exactly what happens (purge all messages) and the scope (LocalStack). No additional details are needed for an agent to invoke it correctly.

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 coverage is 100%, and the only parameter 'queueName' is already described in the schema as 'Queue name'. The description adds no further semantic meaning about the parameter, so it correctly receives the baseline score for high schema coverage.

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 a specific verb ('Purge') and resource ('all messages from an SQS queue'), clearly distinguishing it from sibling tools like sqs_delete_queue (deletes the queue itself) and sqs_delete_message (deletes a single message). It also scopes the action to LocalStack.

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 clearly implies the use case: when you want to remove all messages from a queue. However, it does not explicitly mention alternatives or when not to use this tool (e.g., for deleting individual messages, use sqs_delete_message). Thus it provides clear context but no exclusions.

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