explain_query

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

With no annotations provided, the description carries the full behavioral burden. 'Dry run' and 'before running' strongly communicate that this tool does not execute the query, and the description details the informational output it produces. It could be more explicit about side-effect-free behavior, but the dry-run framing is sufficient.

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 short sentences with no filler. The first sentence front-loads the core behavior, and the second adds a concrete usage scenario. Every word earns its place.

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 adequately explains what the tool does, what it returns, and when to use it, and an output schema exists so return-value details are less critical. However, because the plan parameter is a complex nested object with no schema descriptions, the description leaves the main invocation detail under-specified.

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 only parameter, plan, is an object with additionalProperties allowed and 0% schema description coverage. The description repeatedly references 'the plan' and implies it is a query plan, but it provides no structural guidance about what fields the plan object should contain or how to construct it.

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 a specific verb and resource: it 'Shows the English reading of the plan' and lists the concrete contents shown (definitions, seasons, warnings, SQL). It also distinguishes itself from executing siblings like query and raw_sql by explicitly labeling the operation a 'Dry run', making its non-execution role clear.

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 gives explicit usage context: 'Use it to confirm your interpretation with the user before running an expensive or ambiguous query.' This clearly tells an agent when to invoke it, though it does not name alternatives or explicitly say 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.