list_tickets

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it returns a list of tickets and doesn't mention side effects, permissions, or pagination. Additionally, it says the status filter is optional while the schema requires status, creating ambiguity about runtime behavior when status is omitted.

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 uses a clear :param/:return structure, which is concise. However, the parameter lines duplicate schema information and include an inaccurate 'optional' note, making the structure misleading despite its brevity.

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 two-parameter list tool, the description is incomplete. It doesn't explain allowed status values, pagination, output shape (despite an output schema existing), or the discrepancy between the optional label and the required schema field. An agent would struggle to use this tool correctly without additional information.

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 schema has zero description coverage, so the inline parameter descriptions are the only semantic information. However, they are minimal and partially contradictory: 'employee_id' is described as 'Employee ID' (tautological) and 'status' is marked optional despite being required in the schema. No valid values or default behavior are provided, which is insufficient for an agent to construct a correct call.

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 it lists tickets for an employee, using a specific verb and resource. It is distinct from sibling tools like create_ticket and update_ticket_status, though it doesn't explicitly call out alternatives.

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?

There is no guidance on when to use this tool versus other ticket or employee tools. It doesn't mention any prerequisites, exclusions, or conditions that would help an agent choose this tool over alternatives.

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