get_tickets_by_queue

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

With no annotations, the description carries the full burden. It discloses a key behavioral default (only open/active tickets unless include_completed=True) which adds value. However, it does not mention pagination defaults, per_page limits, ordering, or interactions between date filters and completed status, leaving several behavioral aspects undisclosed.

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-load the core purpose, clarify the domain concept, and state the default behavior. There is no redundant information, and every sentence earns its place.

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?

Given the rich input schema and output schema, the description provides sufficient context for tool selection and basic invocation (queue concept and default status filter). It lacks some higher-level guidance like pagination interactions and comparison with search_tickets, but the overall information is adequate for the tool's complexity.

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 covers 100% of parameters with clear descriptions, so baseline is 3. The description adds minimal semantic context by clarifying that queue maps to TicketCategory and highlighting include_completed, but these are also inferable from the schema. No additional parameter meaning is provided.

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 tool 'Get all tickets in a specific queue' with a specific verb and resource, and notes it retrieves from TicketCategory in Autotask. This distinguishes it from sibling tools like search_tickets or get_ticket_details by focusing on queue-based retrieval.

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 gives clear context: use this tool to retrieve tickets from a specific queue, with optional filtering, and explains the default behavior of excluding completed tickets. It doesn't explicitly mention alternatives or when-not-to-use, but the purpose is sufficiently constrained to guide selection among siblings.

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