servicebus_requeue_subscription_dlq

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

No annotations provided, so description carries full burden. It discloses that messages preserve body, session_id, correlation_id, and application_properties, are completed (removed) after requeue, and stops if max_messages is exceeded. This covers key behavioral traits.

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?

Two sentences: the first states the core action, the second provides behavioral details. No filler, efficiently front-loaded.

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 an output schema exists (not shown), the description covers the tool's function and safety behavior (max_messages guard, message preservation). It omits return value details but that is handled by the output schema. No prerequisites mentioned, but that may be assumed.

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 max_messages as the stop condition and implies namespace, topic, subscription are identifiers via 'topic subscription's dead letter queue'. However, it does not describe valid values or format for the required parameters.

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: 'Move messages from a topic subscription's dead letter queue back to the topic.' It specifies the resource (topic subscription DLQ) and the verb (requeue). This distinguishes it from siblings like servicebus_requeue_dlq (for queue DLQ) and others.

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_peek_subscription_dlq or servicebus_purge_subscription_dlq. The description implies usage for reprocessing dead-lettered messages but does not provide exclusions or context for choosing it.

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