sophos_download_quarantine_attachments

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

The description says 'Initiate a download job,' which implies creating a job (a write operation), but annotations declare readOnlyHint: true. This is a direct contradiction. The description does not resolve this inconsistency and provides little additional behavioral context.

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 a single sentence of 13 words, directly stating the action and output with no unnecessary information. It is optimally concise.

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 tool has 3 required parameters and no output schema, the description is too minimal. It does not explain how to obtain the attachments list, or that the downloadId should be used with sophos_get_quarantine_download_status. The contradiction with annotations further reduces completeness.

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 all parameters are described in the schema. The description adds no extra meaning beyond what the schema already provides, meeting the baseline score.

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 action (initiate a download job), the resource (attachments from a pre-delivery quarantined message), and the return value (downloadId for polling). It distinguishes from sibling tools like sophos_list_quarantine_attachments and sophos_get_quarantine_download_status.

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?

Description implies using this tool to start a download and then poll with the returned downloadId, but does not explicitly state prerequisites (e.g., needing a tenant_id and message_id from other tools) or when to use this vs alternatives like sophos_download_post_delivery_quarantine_attachments.

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