list_tickets

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description states this lists 'top-level tickets' (excluding subtasks), which is useful hierarchical context. However, it does not disclose return format, pagination behavior, ordering, or what happens when no filters are applied (presumably lists all). Given no annotations exist, this is a modest but incomplete disclosure.

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 clear sentence that efficiently conveys the core action and optional filters. No wasted words. It is appropriately sized for a list-type tool.

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 list tool with all-optional parameters and no output schema, the description is reasonably sufficient: it names the action, resource, and two filter dimensions. However, it does not clarify 'top-level' semantics fully (whether subtasks appear, how the default Main board works), nor does it mention the limit parameter or result ordering. Slightly under-specified but adequate for basic use.

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 only 33% (only board_id has a description, noting it defaults to Main board). The description mentions board_id and status filters, reinforcing their meaning, but adds no semantics for limit or status (e.g., what status values are valid). It partially compensates for the low coverage by naming the filter fields, but no enum or syntax guidance is provided for status.

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 the scoping qualifier 'top-level' which helps distinguish it from nested ticket operations. The optional filters (board_id, status) are named. This clearly differentiates from siblings like get_ticket (single fetch), create_ticket, and list_leads. Strong purpose clarity.

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 this is for retrieving ticket lists with optional filtering, but provides no explicit when-to-use guidance or exclusions relative to siblings. It doesn't say 'use get_ticket for a single ticket' or note that dashboard_pulse might serve summary needs. Context of usage is only implicit.

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