sophos_run_saved_xdr_query

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

The description reveals that the tool returns a run ID to poll for status and results, implying an asynchronous operation. However, with no annotations, it lacks details on side effects, permissions, or resource creation. It provides basic transparency but not comprehensive.

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, front-loaded with the action and key outcome. No unnecessary words, efficient and clear.

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 the complexity (7 parameters, no output schema), the description adequately explains the workflow: run a saved query and obtain a run ID to poll. It does not enumerate all optional parameters but relies on the schema for details. This is sufficient for understanding the tool's primary function.

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 parameters are documented in the schema. The description only adds context for the query_id parameter ('saved XDR query to execute'), but does not provide additional meaning beyond the schema for other 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 'Run a saved XDR query' and 'by its query ID', providing a specific verb and resource. It distinguishes from ad-hoc queries by mentioning 'from the query library', but does not explicitly contrast with sibling tools like sophos_run_xdr_query.

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 on when to use this tool versus alternatives such as sophos_run_xdr_query or sophos_run_live_query. It is expected to be used for pre-saved queries, but this is not stated explicitly.

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