tickets_list_comments

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

No annotations provided, so description carries burden. Discloses sorting order (ticket_id ASC, created_at DESC) and explains filter behavior difference (comment-level vs ticket-level date filters). Lacks response structure details due to no output schema.

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?

Extremely concise: one well-structured sentence that front-loads purpose, distinguishes from sibling, and conveys key behavioral details without waste.

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 15 parameters, no output schema, and many siblings, description covers purpose, differentiation, filtering nuances. Missing return field details, but overall adequate for agent decision-making.

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 100%, baseline 3. Description adds value by clarifying that comment_created_after/before filter at comment level while other date filters operate on parent ticket. Also explains 'mine' scope. Adds meaning beyond schema for key parameters.

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?

Describes a specific action: listing ticket comments across multiple tickets, flat paginated feed. Explicitly distinguishes from sibling tool tickets_get_comments which is scoped to one ticket.

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?

Provides explicit alternative (tickets_get_comments) and mentions various scoping filters. Does not explicitly state when not to use, but gives context for appropriate use cases.

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