autotask_get_ticket_attachment

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

Without annotations, the description fully discloses behavioral traits: default metadata-only, optional binary retrieval, size limits, data stripping with dataOmittedReason, and verification against ticketId. No contradictions.

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?

Four dense sentences, each adding unique value. Front-loaded with core purpose, no redundant or filler content. Structure is 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?

Given the complexity of the tool (two modes, size constraints, verification) and no output schema, the description is remarkably complete. It covers all critical aspects and potential pitfalls.

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%, but the description adds critical context like default values, endpoint behavior (top-level vs child), and the effect of maxInlineBase64Bytes. This significantly enhances understanding beyond the schema.

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 verb 'Get' and the resource 'ticket attachment', distinguishing it from sibling tools like autotask_create_ticket_attachment and autotask_search_ticket_attachments. The behavior with includeData parameter is explained, solidifying purpose.

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 excellent intratool guidance (when to use includeData=true vs false, size limits) but does not explicitly state when to prefer this tool over alternatives like autotask_search_ticket_attachments. Intertool guidance is absent.

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