servicebus_purge_subscription_dlq

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

With no annotations provided, the description carries full burden. It discloses destructiveness and the stopping behavior when max_messages is exceeded. It also explains authentication method. Missing details on required permissions or failure scenarios, but adequate for a destructive 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?

The description is concise at 5 lines, with no wasted words. The destructive warning is front-loaded. Each sentence adds value.

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?

Given the destructive nature and 5 parameters, the description covers core purpose and behavior, but lacks explanation for required parameters (namespace, topic, subscription) and does not mention output schema. Could be more complete.

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 0%, so description must compensate. It explains connection_string_env_var's role in authentication, but does not add meaning for namespace, topic, subscription, or max_messages beyond their names. Partial compensation, but gaps remain.

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 the action: deleting all messages from the dead letter queue for a topic subscription. It uses specific verb 'delete all messages' and resource identification. Among sibling tools, it distinguishes from similar operations like peek or requeue.

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 warns that the operation is destructive and messages cannot be recovered, and explains behavior when max_messages is exceeded. However, it does not explicitly contrast with alternative tools like peek or requeue, nor specify when not to use this tool.

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