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 indicates each call is per ticket and warns about iteration, which is helpful. However, it does not disclose whether the operation is read-only, idempotent, or has any side effects. Given the simple search semantics, a score of 3 is appropriate.

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 very concise with two sentences, no fluff, and front-loads the core purpose. The second sentence provides crucial usage guidance. It could be slightly more efficient but is well-structured.

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?

The description is adequate for a simple search tool, but it lacks information about the output format (expected return value). Given no output schema, this is a gap. However, it covers the important behavioral aspect of separate queries per parent ticket.

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 description coverage is 100%, so the schema already documents both parameters. The description adds no extra meaning to the parameters beyond what is in the schema. According to guidelines, baseline 3 is correct.

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's action ('Search for attachments') and the resource ('on a specific ticket'). It distinguishes from siblings by specifying 'ticket attachments' and adds a note about scoping parent tickets, which differentiates it from other search tools.

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 provides explicit guidance: 'scope the parent ticket list before iterating', which helps avoid misuse. It implies when to use the tool (for a specific ticket) but does not list alternatives or explicitly state when not to use it.

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