autotask_list_queues

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

No annotations provided, so description must carry full burden. Description implies a read-only operation (listing) but does not explicitly state side effects or authorization requirements. It is truthful and adequate but lacks depth.

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?

Two sentences, concise and front-loaded. First sentence states primary function, second provides use case. 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?

Tool has no input parameters and no output schema, so description need only explain what it does and how results are used. It does that succinctly. A 5 would require explicit mention that output is a list of queues with IDs and names, but the use case is clear enough.

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?

Input schema has no parameters, so schema_description_coverage is 100%. The description adds value by explaining the purpose of the returned data (queue IDs for filtering), which is not obvious from schema alone. No parameter documentation needed.

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?

Description clearly states the tool lists all available ticket queues in Autotask. It specifies the purpose is to find queue IDs for filtering tickets, which is a specific use case that distinguishes it from siblings like 'autotask_search_tickets' or 'autotask_list_ticket_statuses'.

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 explicitly states to use this tool to find queue IDs for filtering tickets by queue. It does not mention when not to use it or name specific alternatives, but the context is clear given the sibling set includes search tools and other list tools.

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