sophos_preview_post_delivery_quarantine_message

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

No annotations are provided, and the description only says 'Preview the content'. It does not disclose whether this is a read-only operation, what 'preview' entails (e.g., snippet vs full content), required permissions, or any side effects. For a tool with no annotation support, this is insufficient.

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, which is concise but lacks structure. It does not waste words, but it also does not earn its place by providing additional value. A slightly longer description with more detail would improve this dimension.

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 tool with no output schema and no annotations, the description is too brief. It fails to explain what the preview returns (text, HTML, metadata), how it relates to download or release operations, or any prerequisites. The context is incomplete for an agent to use the tool effectively.

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 the input schema already documents both parameters with descriptions. The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 uses the verb 'Preview' and specifies the resource as 'post-delivery quarantined message', which clearly indicates the operation and target. It distinguishes this tool from the similarly named 'sophos_preview_quarantine_message' by specifying 'post-delivery', but it does not explicitly contrast them. The purpose is clear and specific enough.

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 like 'sophos_preview_quarantine_message' or 'sophos_get_post_delivery_quarantine_download_status'. It only states the action, leaving the agent to infer context from sibling names.

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