execute_sql

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

Discloses read-only nature and pagination via limit/offset, which are key behaviors. With no annotations, this is good disclosure, though it doesn't cover error handling or output format details.

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 succinct sentences that front-load the purpose and then add a key detail. No redundant 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?

Covers the main aspects of the tool. With an output schema present, the description is sufficiently complete for a 3-parameter tool, though it omits potential constraints like query length.

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?

Adds meaning to sql_statement by specifying allowed query types and to limit/offset by mentioning pagination, supplementing the schema which has 0% description coverage.

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 restricted to SELECT and WITH statements, distinguishing it from sibling tools that provide specific schema/table info.

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?

Implies when to use (custom read-only SQL queries) and implicitly excludes write queries by specifying SELECT/WITH only, but does not explicitly mention alternatives or when not to use.

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