tickets_list_attachments

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-only listing operation but does not state whether it returns metadata only, whether content download is out of scope, or any auth/pagination behavior. The output schema exists but the description adds no behavioral context beyond the word 'List'.

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?

A single sentence with no filler; the verb and object are front-loaded. Every word earns its place given the simple one-parameter API.

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 one-parameter tool with an output schema, the basic listing intent is adequately conveyed. However, it lacks the relationship to closely related attachment tools (link, upload, delete) and uses 'case' where the parameter is a ticket, leaving agent selection slightly under-informed.

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 already documents the only parameter (ticket_id, 'eSentire ticket number') with 100% coverage, so the baseline is 3. The description adds no extra parameter-level meaning and does not clarify the 'case' phrasing beyond what ticket_id states.

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?

States a specific verb ('List') and resource ('file attachments on a case'), so the operation is immediately recognizable. It is clear enough to separate from upload/delete/link siblings by operation type, but it does not explicitly differentiate from tickets_get_attachment_link, and 'case' vs ticket_id is mildly inconsistent.

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?

No guidance is given about when to use this tool instead of related siblings such as tickets_get_attachment_link or tickets_list_emails. The description relies entirely on the verb to imply intent; there are no exclusions, prerequisites, or alternative routing.

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