sophos_list_xdr_query_runs

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

With no annotations provided, the description carries the full burden of disclosure. It indicates a read operation but does not mention idempotency, rate limits, authentication requirements, or any side effects. The pagination feature is mentioned but not elaborated on.

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 a single sentence of 7 words, highly concise with no redundant information. However, it lacks structural elements like bullet points or sections that could improve readability for complex parameters.

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 tool has 4 parameters with full schema coverage, but no output schema. The description does not explain what the response contains (e.g., list of runs with statuses, timestamps). Given the lack of annotations, more context is needed for an AI agent to understand the tool's behavior fully.

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%, so the baseline is 3. The description adds no additional meaning beyond the schema; the schema already describes all four parameters (page_size, tenant_id, page_total, page_from_key) with clear descriptions.

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 'List' and resource 'XDR query run history', clearly distinguishing it from sibling tools like sophos_list_xdr_queries (listing queries) and sophos_list_xdr_query_categories (listing categories).

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?

No guidance is provided on when to use this tool versus alternatives such as sophos_list_xdr_queries or sophos_get_xdr_query_status. The mention of 'optional pagination' hints at usage but does not provide clear context.

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