get_queue_status

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

With no annotations provided, the description is the sole source of behavioral context. It discloses the read-only nature via 'Get' and spells out what the response covers: total, errors, warnings, and items needing manual interaction. It does not discuss pagination or exact response shape, but for a zero-parameter status tool this is sufficient transparency.

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 a single sentence that front-loads the tool's purpose and then enumerates the meaningful categories of the response. Every word earns its place; there is no filler or redundancy.

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, zero-parameter, no-output-schema tool, the description is complete. It tells the agent exactly what data will be returned and implies the use case clearly. No additional context is needed for correct invocation or interpretation.

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, so the schema fully covers the input surface. The baseline of 4 applies because there are no parameter semantics to document; the description appropriately focuses on output rather than input.

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 states a specific verb ('Get'), the resource ('queue counts'), and the exact dimensions of the result ('by state', total, errors, warnings, manual interaction). This clearly distinguishes it from siblings like get_queue, which would return the full queue list, and get_queue_details, which would return item-level details.

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 makes the use case obvious: use this tool when you need summary counts of queue states rather than the full queue listing. It does not explicitly name alternative tools or state when not to use it, but the wording provides clear contextual routing.

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