list_ticket_attachments

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

Despite no annotations, the description discloses important behavioral traits: returns metadata never bytes, only finished uploads are listed (in-flight/deleted appear absent), and lists newest first. It also notes that the reply carries metadata, not the file content, which is a key limitation beyond the 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?

The description is information-dense yet concise. Each sentence earns its place: it states the output fields and ordering, contrasts with get_ticket_attachment, mentions the attachment_total signal, and clarifies handling of in-flight/deleted files. It's well-structured, starting with the core function.

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?

With no output schema, the description fully describes the return format (metadata fields), ordering, and limitations. It also provides surrounding context (get_ticket for count, get_ticket_attachment for content) that makes the tool's role in the API complete. Nothing critical is missing.

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 has only task_uuid with no description (0% coverage). The description compensates by framing the tool as listing 'files on a ticket', making it clear that task_uuid is the ticket/task identifier. While it doesn't explicitly define the parameter, the context and tool name make its meaning unambiguous.

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 what the tool does: lists a ticket's files with metadata (name, content type, size, uuid) ordered newest first. It distinguishes from get_ticket_attachment (which fetches the bytes) and explicitly says 'Nothing else here reads a ticket's files', making it unique among siblings.

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 usage context: use this to inspect attachment metadata, e.g., checking if a spec is a PDF. It references get_ticket for the attachment_total count to decide if calling is worthwhile, and get_ticket_attachment for fetching bytes, effectively giving alternatives and guidance on when to use each.

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