Execute Sql

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

Because annotations are absent, the description carries the behavioral disclosure burden. It states that the operation is read-only, restricts statements to SELECT/WITH, and notes that results are paginated via limit/offset. It does not cover error behavior or statement-size limits, but the core behavioral traits are disclosed.

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 short sentences with no filler: the first front-loads the core purpose and restriction, and the second states the pagination behavior. Every clause adds useful 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?

For a single-query tool with an output schema, the description covers purpose, allowed SQL, and pagination. The main gap is lack of explicit guidance on parameter edge cases and error behavior, but these are minor given the simple parameter set and existing output schema.

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 0%, so the description must compensate. It adds meaning by defining sql_statement as a read-only SELECT/WITH query and explaining that limit/offset control pagination. This is more than the raw schema types provide, though it does not detail edge cases like null limits.

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 uses a specific verb and resource: 'Execute a read-only SQL query (SELECT/WITH only).' This clearly distinguishes it from the sibling metadata and setup tools, which are about listing, searching, and managing schemas and tables.

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 scope is explicit: only SELECT/WITH queries are allowed, so the agent knows this tool is for read-only querying, not DDL/DML. It does not explicitly name sibling alternatives like list_tables, but the exclusion of writes provides clear enough context for choosing this tool.

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