execute_sql

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

No annotations provided, so description carries full burden. It states the tool is read-only and lists allowed statement types. It does not mention error handling, timeouts, or result format, but the basic behavioral constraint is clear. No contradictions.

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?

Two paragraphs: first explains purpose and constraints, second lists arguments with brief descriptions. No unnecessary words. Front-loaded with key constraints.

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?

Includes constraints on allowed SQL statements and connection_name source. Has output schema (not shown) so return values need not be described. Could mention that connection must exist, but given sibling list_connections, this is implied.

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 has 0% description coverage, so description adds value. For connection_name, it explains it should match names from list_connections. For sql, it reiterates read-only constraint. Could add more detail about SQL formatting or quoting, but sufficient for basic understanding.

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?

Clearly states it executes a read-only SQL query on a database connection. Lists supported statements (SELECT, SHOW, DESCRIBE, EXPLAIN, WITH) and explicitly prohibits write operations. Distinguishes from sibling tools (list_connections, list_workspaces) which are listing tools.

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 that only read-only queries are allowed and write operations are prohibited. Mentions that connection_name should be as shown in list_connections, implying a prerequisite step. Does not explicitly state when not to use the tool, but the context is clear.

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