sophos_get_xdr_query

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it is a safe read operation. The description adds context that it retrieves template details, but does not elaborate on behavior beyond what annotations convey (e.g., no mention of caching, rate limits, or what 'details' include).

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, well-structured sentence that front-loads the purpose. Every word is necessary, with no filler or redundancy.

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 description is complete for a simple read operation with thorough annotations. However, it does not specify what 'details' are returned (e.g., query text, category, tags), which could help the agent decide if additional tools are needed. A brief enumeration would enhance completeness.

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% coverage with clear descriptions for both parameters (query_id and tenant_id). The description does not add any additional meaning beyond the schema; it simply restates that the query ID is used. Baseline score of 3 is appropriate given the schema's thoroughness.

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 action ('Get details') and the resource ('specific saved XDR query template'), and includes the identifier ('query ID'). This distinguishes it from siblings like sophos_list_xdr_queries (listing all) and sophos_run_saved_xdr_query (running the 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?

The description implies usage after obtaining a query ID, but does not explicitly guide when to use this tool versus alternatives (e.g., when to use sophos_list_xdr_queries first, or that this tool is for viewing metadata only). No exclusions or when-not-to-use guidance is provided.

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