get_new_tickets_tool

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

No annotations were provided, so the description carries the full burden—it does clearly state the tool's behavior (returns new/unassigned tickets, honoring an optional queue filter) and the scoping clarification ('unassigned') adds value. However, it does not explicitly declare read-only/side-effect-free behavior, ordering, pagination, or error behavior beyond what the name implies.

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, information-dense sentence with zero wasted words. Every element ('new', 'unassigned', 'optionally filtered by queue') contributes meaning not apparent from the tool name alone.

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 of this simplicity (1 optional parameter, no required params, no nested objects, and an output schema present so return values are documented elsewhere), the description covers the tool's purpose sufficiently. It falls just short of a 5 by not explicitly addressing edge expectations (e.g., behavior with an empty queue name or how results are ordered), but these are minor gaps given the low 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?

Schema description coverage is 100% (the single 'queue' parameter is documented as 'Optional queue name to filter by'). Since the rubric assigns a baseline of 3 when coverage exceeds 80%, and the description adds no additional parameter nuances (e.g., exact-match semantics, format), the baseline of 3 is appropriate.

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 uses a clear verb ('Get'), resource ('tickets'), and precise scope ('new (unassigned)'). The parenthetical defining 'new' as 'unassigned' provides meaningful disambiguation from siblings like get_my_open_tickets_tool and search_tickets_tool, which could otherwise overlap. This matches the 'specific verb+resource+scope, distinguishes from siblings' bar.

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 core use case (retrieve all new/unassigned tickets, with an optional queue filter) is implied clearly by the wording, so an agent can reasonably infer when to invoke it. However, there are no explicit when/when-not statements, exclusions, or named alternatives such as search_tickets_tool or get_my_open_tickets_tool, which would elevate the guidance beyond implication.

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