sophos_get_live_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 tool's safety profile is clear. The description adds value by disclosing the pagination mechanism ('Uses key-based pagination'), which is a key behavioral trait not covered by annotations. No contradictions.

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?

Two concise sentences: first states purpose, second explains pagination. No unnecessary words. Front-loaded with the primary action.

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?

The description covers purpose and pagination but lacks details about the response structure (no output schema) and prerequisites (e.g., query must be completed). Given the tool's complexity (5 parameters, pagination, no output schema), the description is adequate but has gaps that could hinder an agent.

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% with all parameters described. The description adds minimal parameter-specific information beyond the schema; the pagination note ('pass the nextKey from the previous response as page_from_key') partially reinforces the page_from_key description already present. 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 tool's purpose: retrieve results of a completed Live Discover query run. It uses a specific verb ('Retrieve') and resource ('results of a completed Live Discover query run'), distinguishing it from siblings like sophos_get_live_query_status (status only) and sophos_list_live_query_runs (list runs).

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 explains key-based pagination ('pass the nextKey from the previous response as page_from_key'), providing clear usage instructions for pagination. However, it does not mention when to use this tool versus siblings like sophos_get_live_query_status (check completion first) or sophos_cancel_live_query_run (if still running).

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