sophos_get_quarantine_message

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no further behavioral context (e.g., what happens if message not found, auth requirements, or data freshness). Beyond the annotation, there is minimal value.

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?

Single sentence conveys the core purpose with no waste. It is front-loaded with the action. While very concise, it could be slightly more informative without harming conciseness.

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 'get' tool with no output schema, the description does not explain what 'details' includes (e.g., headers, body, attachments). It is minimally sufficient but lacks completeness. Sibling tools like sophos_get_quarantine_message_urls are more specific.

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 description coverage is 100%, with both parameters (tenant_id, message_id) described. The description says 'by ID' but does not add additional meaning beyond the schema. Baseline 3 is appropriate as the schema already covers the parameters adequately.

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?

Description clearly states 'Get details for a specific pre-delivery quarantined message by ID.' It specifies the verb (Get), resource (details of a quarantined message), and the means (by ID). This distinguishes it from sibling tools like sophos_search_quarantine (which searches) and sophos_preview_quarantine_message (which previews), making the purpose unambiguous.

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?

No guidance on when to use this tool versus alternatives. Sibling tools include sophos_search_quarantine, sophos_preview_quarantine_message, and sophos_get_quarantine_message_urls, but the description does not differentiate or mention any when-to-use or when-not-to-use context.

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