servicebus_send_message

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

No annotations are provided, so the description must fully convey behavioral traits. It explains the scheduled_enqueue_time format and auth selection logic, but omits details on success/failure responses, rate limits, idempotency, or error handling. The tool likely has read-only or destructive aspects, but these are not addressed.

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, using short paragraphs to convey key points. It front-loads the main purpose and then covers additional details. A more structured format (e.g., bullet points for parameters) could improve readability, but current length is appropriate.

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 sends messages and has an output schema (presumably returning status), the description covers auth, scheduling, and basic namespace/queue identification. Missing details include expected behavior on failure, message size limits, retries, and return value semantics. Adequate but not comprehensive for a complex Azure resource.

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 8 parameters with 0% description coverage. The description adds value by explaining scheduled_enqueue_time (ISO 8601 format), connection_string_env_var (auth behavior), and namespace format. However, session_id, correlation_id, and application_properties receive no explanation, leaving gaps for an agent.

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 specifies it sends a single message to an Azure Service Bus queue or topic, using a specific verb and resource. It distinguishes itself from siblings like servicebus_send_batch (multiple messages) and various peek/purge tools, making the tool's purpose unambiguous.

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 provides practical context: namespace can be short or FQDN, and auth method is determined by the presence of a connection string environment variable or DefaultAzureCredential. It does not explicitly contrast with sibling tools like servicebus_send_batch, but the single vs. batch distinction is implicit from the name and description.

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