sophos_get_post_delivery_quarantine_download_status

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds that the tool gets status, but it does not disclose additional behavioral traits such as typical response fields, time-to-completion, or error states. Since annotations cover the main safety aspects, a 3 is appropriate.

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, well-structured sentence that immediately communicates the action. It is concise with no unnecessary words, earning a top score.

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 only two parameters, no output schema, and robust annotations, the description is adequate but lacks details about the return format or typical usage context. It meets minimum viability but could be enhanced with expected status values.

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?

The input schema has 100% description coverage for both parameters (tenant_id and download_id), so the schema already explains their meaning. The description adds no extra information about parameters, hence baseline score of 3.

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 tool's purpose: 'Get the status of a post-delivery quarantine attachment download job.' It uses a specific verb ('Get') and resource ('status'), and the tool name further clarifies the context. It is distinct from sibling tools like sophos_download_post_delivery_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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, dependencies (e.g., requiring a prior download initiation call), or scenarios where another tool would be more appropriate. With many quarantine-related siblings, this omission limits agent decision-making.

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