sophos_download_post_delivery_quarantine_attachments

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

Annotations (readOnlyHint: true, destructiveHint: false) already indicate safety. The description adds the behavioral nuance that the tool returns a downloadId for polling, which is useful extra context. No contradictions with annotations.

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 extremely concise: a single sentence with a clarifying second sentence. It contains no redundant information and is front-loaded with the key action.

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's complexity (3 required params, no output schema), the description covers the essential: what it does, what it returns (downloadId), and the resource context. It does not mention error conditions or prerequisites, but the schema and annotations fill most gaps.

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 all parameters are documented in the input schema. The description does not add any additional semantic meaning beyond what is already in the schema properties.

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 post-delivery quarantined message'), and the output ('Returns a downloadId for status polling'). It distinguishes from sibling tools like sophos_download_quarantine_attachments and sophos_get_post_delivery_quarantine_download_status by specifying 'post-delivery' and the initiation nature.

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 hints at usage by mentioning 'for status polling', but it does not explicitly name the polling tool (sophos_get_post_delivery_quarantine_download_status) or provide when-to-use/ when-not-to-use guidance. The usage is implied but not fully articulated.

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