autotask_list_queues

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

Without annotations, the description carries full burden. It correctly implies a read-only operation by stating 'list' and provides no hint of destructive behavior. The transparency is adequate given the tool's simplicity, though it could explicitly state it's safe and has no side effects.

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 concise: two short sentences. The first sentence presents the main action ('List all available ticket queues'), and the second adds immediate context. 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?

For a tool with no parameters, no output schema, and a straightforward listing action, the description fully covers what an agent needs to know: what it does and why to use it. No gaps remain.

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 input schema has zero parameters and 100% schema coverage. With no parameters to document, the description inherently adds no parameter semantics, but the baseline for zero-parameter tools is 4 as it cannot add more value.

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 explicitly states 'List all available ticket queues' which is a specific verb+resource combination. It further explains the use case for finding queue IDs, making the purpose clear and distinguishable from sibling tools like autotask_search_tickets that consume queue IDs.

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 provides explicit guidance: 'Use this to find queue IDs for filtering tickets by queue.' This tells the agent when to use it. While it doesn't mention alternatives or when not to use it, the simple nature of a list-all tool makes this sufficient.

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