sophos_get_xdr_query_status

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

No annotations, but description compensates by listing possible status values (pending, started, finished) and result values (notAvailable, succeeded, failed, timedOut, canceled). This reveals output domain and behavioral outcomes, adding valuable context beyond the schema.

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: first states purpose, second enumerates possible values. No wasted words, front-loaded with key information.

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?

No output schema, but description enumerates possible status and result values, helping the agent understand expected responses. Lacks explanation of relationship between status and result or error handling, but adequate for a simple status check tool with two parameters.

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% (both parameters described). Description does not add further meaning to parameters; the schema already explains run_id and tenant_id adequately. 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?

Description clearly states the tool checks the status of a previously submitted XDR query run, using specific verb and resource. It distinguishes from sibling tools like sophos_get_xdr_query (gets query object) and sophos_get_xdr_query_results (gets results).

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 explicit guidance on when to use this tool versus alternatives. The description implies usage after sophos_run_xdr_query, but does not mention exclusions or provide comparative context with siblings.

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