sophos_get_detection_counts

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

Annotations already mark the tool as readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds the behavioral detail that results are grouped into per-hour or per-day buckets, which is useful but not extensive. Missing details like pagination, limits, or data staleness.

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 two sentences long, front-loaded with the action and key details. Every word is essential; no waste. It efficiently communicates the core functionality.

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 12 inputs and no output schema, the description is somewhat sparse. It doesn't explain the return format beyond 'grouped by severity and type', nor does it mention limits or use cases. For a tool with many filters, more context (e.g., typical usage for dashboards vs. raw queries) would improve completeness.

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 schema already provides detailed descriptions for all 12 parameters. The tool description adds high-level context about time range and resolution but does not substantially enhance understanding of individual parameters. 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 'Get detection counts grouped by severity and type over a time range', specifying the verb (get), resource (detection counts), and key dimensions (severity, type, time range). It also mentions the output format (per-hour or per-day buckets). This clearly distinguishes it from sibling tools that either fetch raw detection data or perform other operations.

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 does not provide any guidance on when to use this tool versus alternatives. There are many sibling tools like sophos_get_detections_query_results or sophos_get_detections_group_results that also deal with detections, but no differentiation is provided. No exclusions or prerequisites are mentioned.

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