query_with_explain

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

With no annotations, the description carries full burden. It indicates the tool runs a query with EXPLAIN ANALYZE, which implies execution of the query, but does not explicitly state that the query is executed (EXPLAIN ANALYZE actually runs the query). No mention of read-only or destructive nature.

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 unnecessary words. Every word adds value.

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 performance debugging tool, the description is adequately clear but lacks details about return values (execution plan, timings) and side effects (actual query execution). Given no output schema and the tool's complexity, it could be more 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?

Schema coverage is 100%, and the schema already describes both parameters well ('SELECT query to analyze', 'Include ANALYZE, BUFFERS, VERBOSE'). The description adds little beyond 'for performance debugging', so baseline 3 applies.

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 the tool runs a query with EXPLAIN ANALYZE for performance debugging, using specific verb, resource, and purpose. It distinguishes from sibling tools like execute_sql and query_db by highlighting the EXPLAIN ANALYZE functionality.

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 implies usage for performance debugging but does not explicitly state when to use this tool versus alternatives like execute_sql or query_db. No exclusions or alternative recommendations are provided.

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