query

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

No annotations are provided, so the description carries the full burden. It discloses truncation with a truncated flag, read-only enforcement, and driver-specific multi-statement behavior. It does not detail error handling or logging, but covers essential behavioral traits for a query tool.

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 concise with three sentences. The first sentence states the purpose and a helpful hint. Subsequent sentences efficiently detail truncation, read-only behavior, and multi-statement handling. No extraneous information.

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?

The description covers key behaviors but lacks details on the return format (e.g., structure of results, handling of errors, or what happens with empty results). Given the absence of an output schema, more information about the response would improve completeness for a query tool.

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%, so baseline is 3. The description adds value by explaining the connection parameter (use connection_list to discover keys), max_rows default from config, and multi-statement driver requirement for query. This goes beyond the schema descriptions, justifying a score of 4.

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 a SQL query on a configured connection, with a hint to discover connection keys. It distinguishes from sibling tools like query_plan and query_to_file by describing query execution behavior.

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 guidance on when to use (e.g., for SQL execution) and mentions prerequisites (use connection_list). It advises adding LIMIT for large tables and explains behavior for read-only connections and multi-statement scripts. However, it does not explicitly list alternatives or conditions to avoid using this tool.

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