servicebus_send_batch

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions batch delivery in a single operation and details message structure, but omits critical information like atomicity (whether the entire batch succeeds or fails), error handling, idempotency, or rate limits. This gap leaves the agent uncertain about important behavioral aspects.

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 very concise, leading with the main purpose and then listing message fields in a clear bullet-like format. No extraneous information, every 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 presence of an output schema (not shown), the description need not detail return values. It covers the required parameters partially but misses behavioral aspects like atomicity. For a batch send tool, the description is adequate but not fully 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?

The input schema has 0% description coverage, so the description adds significant value by detailing the structure of the 'messages' parameter, including required 'body' and optional fields. However, it does not explain 'namespace' or 'queue', relying on context from sibling tools. Overall, strong for the key parameter.

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 tool sends multiple messages in a single batch to an Azure Service Bus queue or topic. It uses a specific verb (send) and resource (multiple messages) and distinguishes itself from the sibling tool servicebus_send_message, which sends a single message.

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 indicates the tool is for sending multiple messages in a single operation and is useful for seeding test data. It implicitly differentiates from sending individual messages, but lacks explicit when-not-to-use or alternative guidance.

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