list_ticket_notes

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

No annotations are provided, and the description carries the full burden of behavioral disclosure. It does not mention read-only nature, error handling, pagination, ordering, or what happens if the ticket does not exist, leaving significant uncertainty for an agent.

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 extremely concise, with a one-sentence purpose followed by a single parameter explanation. It is well-structured, front-loaded, and contains no unnecessary information.

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 simple single-parameter list tool, the description covers purpose and parameter adequately. However, it lacks behavioral details like error conditions, ordering, or pagination, which are not compensated by the existing output schema.

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?

With 0% schema description coverage, the description compensates by explaining that ticket_id is 'the unique numeric ID of the ticket.' This adds meaning beyond the schema's bare type definition, clarifying that the ID is unique and numeric despite being typed as a string.

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 'List all notes attached to a specific ticket' with a specific verb (list), resource (notes), and scope (attached to a ticket). This distinguishes it from sibling tools like list_tickets (lists tickets) and add_ticket_note (adds a note).

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 makes it clear that this tool is for retrieving notes for a given ticket, providing clear context on when to use it. It implies the need for a valid ticket_id and is distinct from sibling tools, though it does not explicitly mention alternatives.

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