list_queue_status

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

The annotations already mark this as readOnly, idempotent, and non-destructive, and the description adds only the phrase 'Read' and an HTTP endpoint. It provides no additional behavioral context, such as what QueueStatus represents or how it relates to queue details.

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 extremely short, front-loaded with the action, and contains no filler. Every element earns its place, though the brevity comes at the cost of contextual richness.

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 zero-parameter read-only endpoint with an output schema, the basic invocation details are present. However, the description never explains what QueueStatus contains or when it should be preferred over list_queue and list_queue_details, so an agent could select the wrong sibling 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?

The tool has zero parameters and an empty input schema, so there is nothing for the description to clarify. The baseline for no-parameter tools is 4, and no deduction is warranted.

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 the action ('Read') and resource ('QueueStatus'), and includes the exact endpoint, so an agent knows what the tool does. However, it does not differentiate QueueStatus from sibling tools like list_queue or list_queue_details, which limits clarity in a crowded tool list.

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?

No guidance is given about when to use this tool versus alternatives such as list_queue or list_queue_details. The description only repeats the endpoint and gives no context for choosing it.

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