sophos_run_live_query

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

No annotations provided, so description bears full burden. It mentions the asynchronous return pattern (run ID for polling) but lacks disclosure of side effects (read-only assumed but not stated), permissions, rate limits, or failure behavior. Critical for a tool executing arbitrary SQL on endpoints.

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 sentences, zero wasted words. First sentence gives purpose, second describes return value. Efficiently front-loaded for quick scanning.

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?

Despite 5 parameters and no output schema, the description omits important details: polling endpoint references, variable usage, endpoint_id formatting, query length limits (already in schema), and expected behavior. Sibling tools suggest follow-up is needed but not referenced.

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?

All 5 parameters have schema descriptions, so baseline is 3. The description does not add new insight beyond the schema (e.g., no clarification on how variables interact with the query or formatting of endpoint_ids).

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 verb 'Run', the resource 'Live Discover SQL query', and the target 'against one or more endpoints'. It distinguishes from siblings like sophos_run_saved_live_query by emphasizing 'ad-hoc' and from retrieval tools by noting it returns a run ID for 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?

Implicitly indicates ad-hoc usage via the description, but does not explicitly state when to use this over sophos_run_saved_live_query or when not to use it. No exclusions or prerequisites mentioned.

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