autotask_get_ticket_attachment

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

Description only states the basic action. Lacks disclosure of behavioral traits such as the effect of the includeData parameter, output format, permissions, or size limits. Annotations are absent, so the description carries full burden but does not provide sufficient detail.

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?

Single sentence, no wasted words. Front-loaded with key information. Efficient and clear.

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?

For a retrieval tool with no output schema, the description should indicate what the tool returns (e.g., metadata, optional file data). It does not specify return format or behavior. Adequate but could be improved with return type details.

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% and describes each parameter's type and basic purpose. The description adds no additional meaning beyond the schema. Baseline 3 is appropriate; would benefit from explaining that includeData controls base64 content inclusion.

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 'specific ticket attachment', along with the required identifiers (ticket ID and attachment ID). It distinguishes from sibling tools like search (which lists attachments) and create (which creates attachments).

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_search_ticket_attachments. Does not specify context, exclusions, or prerequisites.

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