sophos_get_quarantine_message

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

No annotations are provided, so the description carries the full burden. It only says 'Get details', indicating a read operation, but does not disclose any behavioral traits such as required permissions, rate limits, or side effects. Minimal disclosure for a tool with no 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 a single sentence of 11 words, concise and front-loaded. It efficiently communicates the core action, but could potentially add a bit more context without becoming verbose, such as the type of details returned.

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 there is no output schema, the description should explain what details are returned (e.g., subject, sender, status). It does not. The distinction from sophos_get_quarantine_message_urls is unclear. For a simple read tool, the description is incomplete.

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 the input schema already describes both parameters (tenant_id, message_id) as UUIDs. The description adds no additional meaning beyond 'by ID', which is already clear from the parameter names. Baseline 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 clearly states the verb 'Get', the resource 'pre-delivery quarantined message', and the method 'by ID'. It distinguishes from sibling tools like sophos_search_quarantine (which lists or searches) and sophos_get_quarantine_message_urls (which gets URLs).

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 use when you have a specific message ID and want details, but does not explicitly state when to use it versus alternatives like sophos_search_quarantine. No prerequisites, exclusions, or alternative tool names are mentioned, which would be helpful given the many quarantine-related siblings.

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