servicebus_purge_subscription_dlq

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

With no annotations provided, the description carries the full burden. It clearly states the destructive nature, irreversibility, and the behavior of stopping when max_messages is exceeded, disclosing key behavioral traits beyond the basic operation.

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 short with two sentences and a bold warning line, front-loading the critical destructive aspect. It is concise but could include brief parameter explanations without adding fluff.

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 no annotations, 4 parameters with zero schema descriptions, the description partially completes the picture by explaining destructiveness and max_messages behavior. However, it omits explanations for three required parameters, leaving gaps in context.

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 the description must compensate. It explains the role of max_messages ('stops... if running total exceeds max_messages'), but fails to describe namespace, topic, and subscription, which are required and lack 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 explicitly states 'Delete all messages from the dead letter queue for a topic subscription,' providing a specific verb and resource, clearly distinguishing it from sibling tools like servicebus_purge_subscription (purges main queue) and servicebus_peek_subscription_dlq (peeks).

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 of destructiveness and mentions the max_messages limit, providing context for when it might be used, but does not explicitly guide when to use versus alternatives like servicebus_peek_subscription_dlq or servicebus_requeue_subscription_dlq.

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