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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the notion of 'full details' (rich message body/properties rather than counts), but says nothing about whether peeking is non-destructive on the broker side, the maxMessages cap of 20, or ordering/truncation behavior — all relevant for a message-inspection tool.

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?

One short sentence, front-loaded with verb and resource, with zero filler. It is arguably too terse for a nine-parameter tool, which is why it falls short of 5 — brevity here edges into under-specification rather than pure efficiency.

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 need not be explained. But for a nine-parameter tool with mutually exclusive queue/topic addressing and a dead-letter mode that duplicates a dedicated sibling, the description leaves key selection decisions unaddressed. The agent has to open the schema and cross-read sibling names to call this correctly.

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 100%, so all nine parameters are documented in the schema itself and a baseline of 3 applies. The description adds no extra semantics beyond that — it does not explain that queueName and topicName are alternative addressing modes, nor mention subscriptionName or the dead-letter toggle.

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?

States a concrete verb and resource: 'Inspects messages in queues and topics with full details.' That is clearly a read/peek operation on Service Bus messages, and the GUI analogy reinforces the 'show me everything' intent. However, it never distinguishes itself from siblings that also surface message content, notably azure_servicebus_dlq_content and azure_servicebus_queue_deadletter, which the peekDeadLetters parameter overlaps with.

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?

There is no when-to-use guidance at all — nothing says to reach for this instead of azure_servicebus_queues (discovery), azure_servicebus_queue_metrics (counts), or azure_servicebus_dlq_content (dead letters). The only hint is the GUI comparison, which is descriptive rather than directive. The agent must infer routing from the name alone.

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