explain_query

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

Discloses that ANALYZE executes the query, a key behavioral trait. However, lacks details on side effects, authorization needs, or limitations (e.g., read-only mode noted in schema but not description). Without annotations, more context is expected.

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?

Extremely concise at two sentences with front-loaded main purpose. No redundant wording, 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?

Covers core purpose and a critical side effect. However, missing context on when to use vs siblings, and no mention of format or analyze implications beyond execution. Given an output schema exists, return values are covered, but usage context is incomplete.

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% with descriptions for all parameters. The description adds value by explaining the 'analyze' parameter's execution side effect, which is not fully captured in schema. For 'format' and 'sql', it relies on schema, which is adequate.

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 it returns an EXPLAIN plan for a query, using specific verb+resource. It distinguishes from sibling tools like execute_query by hinting at planning versus execution, though it does not explicitly differentiate.

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 guidance on when to use this tool over alternatives like execute_query or describe_table. No context about prerequisites or typical scenarios is provided.

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