find_image_attachments

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

No annotations are provided, so the description carries the full behavioral burden; it does disclose that the scan is multi-ticket and filters to png/jpg/jpeg, but says nothing about permissions, result caps, pagination, or how null/empty ticket_ids behaves. The workflow hints at the read-only downstream OCR use, but the disclosure stops short of what an unannotated tool ideally needs.

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 core capability is front-loaded in the first sentence, and the workflow is compact and scannable with no filler. The numbered steps add length but each line carries routing value, so it stays efficient.

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 an output schema present and only one input parameter, the description does not need to explain return values, and its workflow covers the integration path. The remaining gap is behavioral detail (limits, null handling, auth) that no annotation supplies.

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 0%, and the description only implies that ticket_ids is a plural collection to scan, adding nothing about format, null semantics, size limits, or whether an empty list means 'all'. The parameter name is largely self-explanatory, but the description does not compensate for the documentation gap.

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 names a specific verb (scan/return) and resource (image attachments on multiple tickets) and constrains the output to png/jpg/jpeg, so the agent knows exactly what it retrieves. It is clearly distinguishable from single-ticket list_attachments and from get_attachment_text by being the bulk multi-ticket image filter.

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 numbered workflow places the tool precisely between search_tickets (to obtain IDs) and get_attachment_text (to OCR), which tells the agent when to reach for it. It lacks an explicit when-not clause (e.g., use list_attachments for a single ticket), so it falls just short of a 5.

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