sophos_start_detections_group_query

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 discloses the async behavior and the need to poll for results, which is good. However, it does not mention authorization requirements, rate limits, or what happens if multiple queries are started. The description is adequate but not exhaustive.

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 three sentences, front-loaded with the core purpose and then adding key details (grouping, async, return value). No redundant information; every sentence adds value.

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 no output schema and no annotations, the description provides essential context: it explains the tool's purpose, async nature, and that a run ID is returned for polling. It could explicitly reference the polling tools (e.g., sophos_get_detections_group_status), but the description is largely complete for an agent to understand the workflow.

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%, so the baseline is 3. The description adds no extra context for the parameters beyond what the schema already provides (e.g., sort, severity range). The description does not improve parameter understanding.

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 a specific verb 'Start' and resource 'async detection-groups query run'. It clearly explains that the tool groups detections by detection rule and device for a summary view, and that it returns a run ID. This distinguishes it from sibling tools like sophos_start_detections_query (ungrouped) and sophos_get_detections_group_results (polling).

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 mentions async and polling, implying usage for retrieving grouped results later, but it does not explicitly state when to use this tool versus alternatives like sophos_start_detections_query. No exclusion criteria or comparison to other tools is provided.

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