sophos_cancel_xdr_query_run

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

Annotations already indicate readOnlyHint=false (mutation) and destructiveHint=false (no data destruction). The description adds only the HTTP method (POST) and sub-resource (/cancel), which are minor implementation details. It does not disclose important behavioral aspects such as whether cancellation is irreversible, what happens to results, or permission requirements.

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 extremely concise with two sentences containing no extraneous information. Every word serves a purpose, making it easy to parse quickly.

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 simplicity of the tool and no output schema, the description lacks critical context about the lifecycle of query runs (e.g., what states are cancellable, what errors might occur, how to verify cancellation). It does not relate to sibling tools like sophos_run_xdr_query or sophos_get_xdr_query_status, leaving an incomplete picture.

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?

The input schema has 100% description coverage for both parameters (run_id and tenant_id). The description does not add any additional meaning or context beyond the schema, so it meets the baseline for parameter semantics.

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 cancels a running or pending XDR query run, specifying the verb 'cancel' and resource 'XDR query run'. This distinguishes it from the sibling tool sophos_cancel_live_query_run, which targets live queries.

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 provides no guidance on when to cancel a query or when to use this tool versus alternatives like sophos_cancel_live_query_run. It does not mention prerequisites (e.g., the run must be in a cancellable state) or any conditions under which cancellation is appropriate.

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