execute_query

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds specific constraints: only SELECT and EXPLAIN PLAN are permitted, and CTEs are accepted. It also notes connections have readonly status via the list_schemas hint. 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 three short sentences, front-loaded with the core purpose, and every sentence adds value. It avoids fluff and is highly scannable.

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?

Given the output schema exists and annotations cover safety, the description is complete for a query tool. It covers statement types, CTE support, and connection discovery. It does not mention pagination or bind parameters, but those are well-documented in the schema, so the description need not repeat them.

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 100%, so the baseline is 3. The description adds a little context around the query parameter (read-only, CTE acceptance) and connection (readonly status), but largely repeats what the schema already states. It does not meaningfully enhance parameter understanding beyond the schema.

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 executes read-only SQL queries (SELECT and EXPLAIN PLAN only), with CTEs accepted. It distinguishes from sibling tools by emphasizing read-only, which contrasts with insert_query, update_query, delete_query, call_procedure, and execute_unsafe_query.

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 provides clear context: it is for read-only SQL queries, and explicitly says to use list_schemas to see available connections and their readonly status. It does not explicitly name write tools as alternatives, but the read-only restriction and sibling names imply 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.