autotask_create_ticket_attachment

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

With no annotations, the description fully covers behavioral traits: explains why base64 encoding is necessary (MCP JSON-RPC), mentions the 3 MB hard limit from Autotask, states that the tool validates the decoded size before the API call and returns a clear error if exceeded. This gives the agent full understanding of constraints and preconditions.

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 three sentences plus one example line, all front-loaded. It starts with the core purpose, then explains the encoding constraint and size limit, and ends with a helpful example. No extraneous words; every sentence adds essential information.

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 covers the main inputs, encoding, size limit, and error behavior. However, it does not specify what the tool returns on success (e.g., attachment ID, confirmation). Given no output schema, this missing detail could leave the agent uncertain about the response format. Still, the description is sufficiently complete for safe invocation.

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 baseline is 3. The description adds value by explaining the rationale for base64 encoding (via MCP limitation), restating the size limit, and providing a concrete example that maps parameters to values. This goes beyond the schema's minimal descriptions.

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 explicitly states the action ('Upload a file attachment to an existing ticket') and identifies the resource (file attachment for a ticket). It distinguishes from sibling tools like autotask_create_ticket_note by focusing on file attachment, and provides concrete details (base64 encoding, size limit).

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 implies usage when attaching files to tickets and provides context (base64 required, 3 MB limit) but does not explicitly state when to use this tool over alternatives or specify scenarios to avoid. The sibling list includes other creation tools, so the differentiation is clear from the tool name.

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