servicebus_purge_queue

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

No annotations, so description carries full burden. Discloses destructive behavior, early stop condition, and auth mechanism. Lacks details on rate limits or return behavior, but sufficient for a purge tool.

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?

Four concise sentences, each serving a purpose: action statement, destruction warning, stopping condition, auth explanation. No unnecessary text.

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?

Covers essential purpose, destruction warning, and key behavior. With an output schema likely present, return values need not be described. A brief note on potential latency could enhance completeness.

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 0%, description partially compensates by explaining connection_string_env_var and implicitly referring to max_messages. However, namespace and queue parameters remain unexplained without 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 states it deletes all messages from an Azure Service Bus queue. It highlights the destructive nature and distinguishes from sibling tools like peek or list operations.

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?

Explicitly warns of irreversibility and mentions stopping condition based on max_messages. Does not explicitly state when to use vs alternatives but context is clear.

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