explain_query

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

No annotations are provided, so the description must convey behavioral traits. It only mentions 'read-only,' which suggests safety, but it does not state whether the query is actually executed, what permissions are required, or any side effects. The behavior of generating a plan without executing is implied but not explicit.

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, front-loaded sentence with no redundant words. It efficiently conveys the core purpose.

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?

While the output schema exists and return values need not be explained, the description lacks usage guidelines and parameter semantics. With no annotations and minimal parameter documentation, the overall context is incomplete for an agent to invoke the tool correctly.

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 description coverage is 0%, and the description does not explain the 'sql' or 'database' parameters. The parameter names are self-explanatory to some degree, but there is no guidance on how 'database' is used or what values are valid, leaving ambiguity.

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 'Return the database query plan for a read-only SQL query' clearly specifies the verb+resource (return the query plan) and distinguishes the tool from siblings like execute_query by focusing on the plan rather than execution results.

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 'for a read-only SQL query' implies the tool is intended for read-only queries, but there is no explicit statement of when to use this tool versus execute_query or other siblings. No exclusions or alternatives are mentioned.

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