autotask_search_ticket_attachments

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

With no annotations, the description carries the full burden. It implies this is a read-only operation (search/read), which is accurate. However, it does not disclose pagination behavior beyond the pageSize parameter, or whether results are sorted or filtered.

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 sentence, which is concise. However, it could benefit from a brief note on scope (only for a specific ticket) to improve clarity.

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 100% schema coverage and the simplicity of the tool (2 params, no output schema), the description is adequate but not complete. It does not mention that 'search' likely returns a list of attachments, nor does it provide any usage example or note about field searching.

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 is 100%, so the description adds little beyond what the schema provides. It does not explain the relationship between ticketId and the search (i.e., it returns attachments belonging to that ticket). The pageSize parameter is described in the schema, and the description adds no extra context.

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 the tool searches for attachments on a specific ticket, distinguishing it from sibling tools like 'autotask_get_ticket_attachment' which retrieves a single attachment by ID. However, it does not explicitly mention that the search is scoped to a single 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?

No guidance on when to use this tool versus alternatives like 'autotask_get_ticket_attachment' (for known attachment IDs) or listing all attachments. Does not explain search semantics, such as whether it performs text search or just returns all attachments.

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