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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false and an output schema exists, so the safety profile is fully covered elsewhere. The description adds nothing beyond scope – no note on namespace-wide enumeration cost, pagination, or empty-result behavior.

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?

A single front-loaded sentence with zero filler. It is appropriately sized but borders on under-specified rather than padded, so it loses a point for thinness rather than verbosity.

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?

For a simple read-only list tool whose annotations and output schema are rich, the description is minimally sufficient to call it correctly. It still omits how results relate to sibling queue-level tools and whether the namespace must be resolved first, leaving an agent to guess the intended workflow.

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 four parameters (namespace, context_id, resourceGroup, azure_tenant_id) are already documented in structured form. The description mentions the namespace implicitly but adds no semantics beyond the schema; baseline 3 applies.

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 specific verb and resource ('Lists all queues') plus a scope ('in a namespace'), which implicitly separates it from the azure_servicebus_topics / topic_subscriptions siblings. It never names those siblings explicitly, so the differentiation is inferred rather than stated.

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, no prerequisites (e.g. that a namespace must be known first, likely via azure_servicebus_namespaces), and no routing to related siblings such as azure_servicebus_queue_metrics, azure_servicebus_queue_deadletter, or azure_servicebus_message_explorer.

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