sophos_get_detections_query_results

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description only needs to add non-obvious behavioral context. It adds the necessary condition that the query must be completed before calling, which is useful and not captured in structured fields. 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 with two short sentences. The key information is front-loaded: purpose first, then usage condition. Every sentence adds value without redundancy.

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 simple role in a polling workflow, the description is complete enough. It covers what it does and when to call it. No output schema exists, but the return type is implicit (query results). The sibling list is large, but the description clearly positions this tool within the detection query sequence.

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% for 4 parameters, so the description does not need to add parameter details. The description adds no parameter-specific information beyond what the schema provides, meeting the baseline expectation.

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 gets results of a completed detections query, with a specific verb (Get) and resource (results of a detections query). It implicitly distinguishes from sibling tools like sophos_start_detections_query and sophos_get_detections_query_status by focusing on retrieving results after completion.

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 explicitly specifies when to use this tool: 'Only call after sophos_get_detections_query_status returns status="finished".' This is a clear precondition that guides the agent to invoke it only at the correct step in the workflow, distinguishing it from other query-related tools.

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