servicebus_list_queues

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

No annotations provided; description discloses output format (sorted JSON array), namespace handling, and authentication behavior. Does not mention error cases or rate limits, but acceptable for a read-only list 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?

Three concise sentences front-loaded with purpose, then output format, then parameter details. No wasted words.

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?

Output schema exists, so return values are covered. Description covers purpose, namespace handling, and authentication. Lacks mention of pagination limits or error scenarios, but minor for this tool.

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?

Adds significant meaning beyond schema: explains namespace short name vs FQDN and automatic suffix, and connection_string_env_var's role in authentication. Schema coverage is 0%, so description carries full parameter documentation.

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?

Clearly states verb 'List', resource 'queues', and scope 'in a namespace'. Distinguishes from sibling tools like servicebus_list_namespaces and servicebus_list_topics.

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?

Provides guidance on namespace format and authentication methods, but no explicit when-to-use or alternatives compared to siblings like other list tools.

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