servicebus_send_batch

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

No annotations provided, so description carries full burden. It discloses batch send behavior, message structure, and auth method. However, it does not mention failure handling, partial success, rate limits, or atomicity, which are relevant for a batch 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 relatively short and front-loads the purpose. Bullet points for message fields are clear. Could be slightly more concise, but no wasted information.

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?

An output schema exists, so return values are covered. The description covers sending, message format, and auth. It lacks details on error behavior and transactional guarantees, which are somewhat important for batch operations.

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 adds meaning for 'messages' (lists expected fields) and 'connection_string_env_var' (explains auth). It does not elaborate on 'namespace' or 'queue', but their purpose is clear from context.

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 it sends multiple messages to an Azure Service Bus queue or topic in a single batch. It distinguishes from siblings like servicebus_send_message and other peek/purge tools by highlighting batch capability.

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?

It mentions 'useful for seeding test data' and implicitly differentiates from servicebus_send_message by explaining batch behavior. It does not explicitly provide when-not-to-use or alternative tools, but the context of sibling tools helps.

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