servicebus_purge_subscription

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

Despite no annotations, the description discloses key behavioral traits: destruction irreversibility, the max_messages limit effect (stops purging if exceeded), and authentication fallback. It does not cover error states or concurrency, but the provided details are valuable and accurate.

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 (5 sentences) and front-loaded with the core purpose in the first sentence. Every sentence adds value: warning, max_messages behavior, and connection_string_env_var details. 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?

Given the tool's complexity (5 parameters, destructive, no annotations, output schema exists), the description covers essential aspects: destructive nature, limiting behavior, and auth. It omits prerequisites or error handling, but the presence of an output schema reduces the need for return value explanations. Overall, it is sufficiently complete for an agent to use effectively.

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%, but the description explains the behavior of max_messages (stops if limit exceeded) and connection_string_env_var (auth method fallback), adding meaning beyond schema properties. Namespace, topic, and subscription are self-explanatory from their names.

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 'Delete all messages from an Azure Service Bus topic subscription,' identifying the exact resource (topic subscription) and action (delete all messages). It distinguishes from sibling tools like servicebus_purge_subscription_dlq by not mentioning DLQ, implying it operates on the main subscription.

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, but does not provide explicit guidance on when to use this tool versus alternatives such as peek or requeue. Usage is implied (to clear a subscription), but no when-not-to-use or alternative suggestions are given.

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