wetrack_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 discloses filter semantics, pagination behavior via page/limit, and default sort order, but does not explicitly state that this is a read-only operation. 'List' implies non-mutating, so the omission is not misleading, but a one-line confirmation would be stronger.

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 front-loaded with the main purpose, followed by a compact Args list where each parameter has exactly one line. There is no fluff or repetition; every sentence adds actionable details. Despite the length needed for 14 parameters, the structure is remarkably efficient.

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 high complexity (14 parameters, all optional, 0% schema descriptions, no annotations), the description is very complete. It covers every parameter meaning, filter behavior, and response view options. It does not explicitly explain interactions between filters (e.g., whether sprint_id and is_backlog are mutually exclusive), but an output schema covers return format and the core usage is not left to guesswork.

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% because no parameter descriptions exist in the JSON schema, leaving the description as the sole semantic source. The description documents all 14 parameters, their formatting (e.g., comma-separated IDs), allowed values (e.g., ticket_type: EPIC/STORY/TASK/BUG, due_date buckets), and special helpers like sprint_id='unassigned' for backlog. This fully compensates for the schema gap.

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 opens with a specific verb and resource: 'List and filter tickets', and clarifies the scope to 'work items and support tickets'. This clearly distinguishes it from sibling tools like wetrack_get_ticket (single ticket) and wetrack_search, so an agent can select it correctly without opening schemas.

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 purpose 'List and filter tickets' implies when to use it, especially since sibling names such as wetrack_get_ticket and wetrack_search make the alternatives clear. However, there is no explicit statement of when not to use this tool or which sibling to prefer (e.g., wetrack_search for keyword search across resources).

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