get_new_tickets_tool

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

With no annotations, the description carries the full burden. 'Get' implies a read operation but there is no explicit statement about side effects, authorization, pagination, ordering, or potential large result sets. This is a minimal disclosure for a list-all tool.

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 short and front-loaded, with a clear summary followed by Args and Returns sections. It is efficient, though the Returns line partially duplicates what the output schema would convey.

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 one optional parameter and an existing output schema, the description covers the essential call contract: what is returned, the optional filter, and the core scope. Minor gaps remain around pagination and default queue semantics, but the core use is clear.

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 coverage is 0%, and the description compensates by explaining that 'queue' is an optional queue name used for filtering. It adds meaning beyond the schema's bare string type, but it does not provide details like valid queue names, case sensitivity, or behavior when the default empty string is used.

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'), a clear resource ('new (unassigned) tickets'), and a scoping filter ('optionally filtered by queue'). This clearly distinguishes it from siblings like get_my_open_tickets_tool or search_tickets_tool.

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 implies usage: when you need all unassigned tickets, optionally scoped by queue. However, it does not explicitly mention when not to use it or which sibling tools would be better for related cases, leaving the routing largely to inference.

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