xql_explain

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

No annotations are provided, so the description carries the burden. It discloses the output type (execution plan and explanation) but does not explicitly state that the query is not executed, nor describe any side effects, permissions, or error behavior. Given the tool's simplicity, this is adequate but not rich.

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 15-word sentence that leads with the key actions and includes the output in a compact, easily parsed format. No wasted words.

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?

For a tool with one parameter, no output schema, and no annotations, the description provides the essential information: what it does and what it returns. It lacks guidance on when to choose this over related tools, but the core functionality is complete.

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 schema description 'Raw XQL query text' fully covers the single parameter, so baseline is 3. The tool description reinforces that the input is an XQL query but adds no additional syntactic or semantic detail beyond the schema.

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 uses specific verbs 'Parse and plan' and identifies the resource as 'an XQL query'. It clearly differentiates from siblings (xql_validate, xql_run) by stating it returns an execution plan and explanation, which is neither validation nor execution.

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 usage guidance or alternatives are mentioned. The description's implied use case is understanding query execution, but it does not contrast with xql_validate or xql_run or state when not to use it.

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