list_tickets

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

With no annotations, the description carries the full burden. It states the action ('List tickets') and return type, but does not explicitly confirm read-only behavior, side effects, or how the optional parameters affect the result (e.g., whether omitting employee_id returns all tickets).

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 brief and front-loaded, with a single purpose sentence and concise parameter/return annotations. It avoids fluff, but is under-informative.

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?

The description leaves ambiguity about the optional parameters: it says 'for an employee' but employee_id is optional, and does not clarify what happens when filters are omitted. It also omits allowed status values. Despite having an output schema, the description is incomplete for a tool with optional filters.

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 description provides only basic restatements of the parameter names ('Employee ID', 'Ticket status') and marks them optional, adding little meaning beyond the schema. It does not specify allowed status values or the behavior when omitted.

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 specific verb ('List') and resource ('tickets'), and adds scope ('for an employee') with an optional status filter, clearly distinguishing it from sibling tools like create_ticket and update_ticket_status.

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 for reading tickets, and mentions the optional status filter, but does not explicitly state when to use this tool versus creating or updating tickets, nor any prerequisites or exclusions.

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