query_sql

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

The description notes the tool is read-only and mentions response metadata (connection, dialect). However, it does not explain how to pass the SQL query given the empty input schema, which is a significant behavioral gap. Without annotations, the description should disclose this mechanism.

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 brief, front-loaded with the main purpose, and every sentence adds value. No wasted words.

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 no output schema and no parameters, the description fails to explain how the SQL query is actually provided to the tool (e.g., via a param not in schema, or from conversation context). This is a critical omission for correct invocation.

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?

With 0 parameters and schema coverage 100%, the description adds value by explaining the tool's constraints and dialect guidance, though it could clarify how the query is supplied.

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's purpose: 'Execute a read-only SQL query against the target connection.' It specifies permitted keywords (SELECT, WITH, EXPLAIN) and mentions dialect support, making the purpose very clear and distinguishable from siblings.

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?

Explicitly states when to use this tool (read-only queries) and what is permitted. It provides dialect guidelines and a default LIMIT, giving the agent clear instructions on how to craft the query.

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