sophos_list_xdr_queries

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only nature is covered. However, the description adds no additional behavioral context such as pagination behavior, result ordering, or that the list is scrollable via page_from_key. The entire description merely restates the tool's function.

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?

A single, front-loaded sentence conveys the core purpose without extraneous words. Every word is necessary and efficiently communicates the tool's function.

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?

Despite good annotations, the description lacks important context for a paginated list tool. It does not mention that results are paginated, what the output looks like (e.g., an array of query templates), or how to handle pagination. The description is too sparse for a tool with 3 parameters and no output schema.

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 all 3 parameters (tenant_id, page_size, page_from_key), so the schema already explains their meaning. The description adds no further parameter semantics beyond what is provided.

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 verb 'List' and the resource 'saved XDR query templates' with scope 'available for the tenant'. It distinguishes from sibling tools like sophos_get_xdr_query (which retrieves a single template) and sophos_run_saved_xdr_query (which executes a 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 explicit guidance on when to use this tool versus alternatives. Does not mention that this is a prerequisite for running a saved query or that it returns a list for selection. The context is only implied.

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