servicebus_requeue_subscription_dlq

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

The description details message preservation (body, session_id, correlation_id, application_properties), the removal from DLQ after requeue, the stop condition when max_messages is exceeded, and authentication behavior based on connection_string_env_var. Since no annotations are provided, the description carries the full burden and does so thoroughly.

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 two concise paragraphs: first explaining the action and key behaviors, second focusing on the authentication parameter. No superfluous text, though the second paragraph could be integrated more seamlessly. It is front-loaded with the core purpose.

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?

Despite an output schema being present, the description does not mention what the tool returns (e.g., count of requeued messages, success/failure). It also does not describe all parameters thoroughly; only one of five parameters receives detailed explanation. For a tool with 5 parameters and no schema descriptions, this is insufficient.

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%, so description must add meaning. It explains connection_string_env_var and its role in authentication, and implicitly clarifies max_messages via the stop condition. However, namespace, topic, and subscription are not explicitly described beyond their names, leaving potential ambiguity for agents unfamiliar with Azure Service Bus.

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 'Move messages from a topic subscription's dead letter queue back to the topic', specifying the source, destination, and action. It distinguishes from sibling tools like servicebus_requeue_dlq (operates on queue DLQ) and servicebus_purge_subscription_dlq (removes without 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?

No explicit guidance on when to use this tool versus alternatives like servicebus_requeue_dlq or peek-then-requeue flows. The stop condition based on max_messages is mentioned but not in a decision-making context. Prerequisites or when-not-to-use are absent.

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