sqs_delete_queue

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

The annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds only that the queue is 'emulated', saying nothing about permanence, what happens to in-flight messages, or error behavior on a missing queue — a notable gap even against the lowered annotation-covered bar.

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?

A single six-word sentence with zero waste and the key verb front-loaded. It is terse without being redundant, though the brevity shades into under-specification rather than tight, information-rich concision.

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 destructive mutation with an undocumented identifier parameter and no output schema, the description should at minimum clarify the queue identifier format and confirm whether deletion is permanent. Neither is present, so an agent cannot call it correctly on the first try without outside knowledge.

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 single required parameter 'queue' has 0% schema description coverage, so neither structured data nor the description says whether it expects a queue name, URL, or ARN. The description provides no compensating detail, leaving the only input's format entirely to guesswork.

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?

States a specific verb (Delete) and resource (SQS queue), so an agent knows exactly what the tool does. It does not name or contrast with any sibling such as sqs_delete_message or dynamodb_delete_table, which keeps it from a 5, but the purpose itself is unambiguous.

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?

There is no when-to-use guidance, no precondition (e.g. queue must exist or be empty), and no mention of alternatives for purging versus removing a queue. The agent must infer everything about invocation context from the verb alone.

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