sophos_get_live_query_results

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

The description adds the pagination mechanism (key-based with nextKey and page_from_key), which is a behavioral trait. However, it does not disclose other aspects like read-only nature, rate limits, or what happens if the query is not yet completed. Since no annotations are provided, the description carries the full burden but falls short.

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 with no waste. The first sentence states the purpose, the second explains pagination. Front-loaded and efficient.

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?

For a tool with 5 parameters and no output schema, the description is too brief. It does not explain what the response contains (e.g., rows of query data), how pagination limits work, or error conditions. The agent lacks sufficient context to use the tool confidently without external documentation.

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 descriptions for all parameters. The description adds value by explaining the pagination usage (page_from_key) beyond the schema, which improves understanding of parameter relationships.

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 it retrieves results of a completed Live Discover query run, using specific verb and resource, and distinguishes from sibling tools like get_live_query_status.

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 implies usage for retrieving results after a query completes, but does not explicitly state when not to use it or provide alternatives. It lacks explicit when-to-use or when-not-to-use guidance.

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