Run WIQL

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

Annotations already declare the tool read-only and idempotent, covering the safety profile. The description adds meaningful behavioral context by stating that the query is executed as-is and that results are returned flat for flat WIQL queries or as a link tree for tree/oneHop queries. No contradiction with annotations.

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 two sentences with the core purpose front-loaded, followed by one illustrative example and a compact note about return shape. There is no filler, repetition, or unnecessary detail.

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 schema fully covers parameter semantics, annotations cover read-only and idempotent behavior, and the description states the return shape. Since there is no output schema, the explicit mention of flat versus tree/oneHop results is valuable; the only notable gap is the absent routing guidance for choosing between run_wiql and run_query.

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 coverage is 100%, so the schema already documents all five parameters with descriptions. The tool description does not explain individual parameters beyond the schema, and its WIQL example only lightly illustrates the wiql parameter. This matches the baseline for full schema coverage.

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 states a specific action ('Execute'), a precise resource ('arbitrary WIQL query string'), and provides a concrete example with a SELECT query. It also distinguishes itself from siblings like run_query by emphasizing raw, as-is WIQL execution rather than saved-query 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?

The phrase 'arbitrary WIQL query string as-is' implies that this tool is for raw query text rather than saved queries, but it does not explicitly mention when to use it versus alternatives such as run_query. No exclusions or routing guidance is given, so usage is only implied.

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