run_select

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

No annotations are provided, so the description carries the disclosure burden. It does reveal two behaviors: max rows are enforced and read-only role is preferred. However, it does not explain what happens when the limit is reached, whether queries can time out, or what the response shape is.

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?

A single sentence that front-loads the action and packs essential constraints into a parenthetical. No wasted words or redundant restatement of the schema.

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 tool is relatively simple and the description covers the core execution contract, but there is no output schema and no mention of return format, error behavior, or when a sibling tool would be a better choice. The description is adequate but not fully complete.

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 add meaning to the parameters. It adds meaning to max_rows ('enforced') and implies sql should contain a SELECT statement. It does not clarify optionality, defaults, or SQL formatting, so compensation is only partial.

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 names a precise verb and resource: execute a single SELECT statement. It also distinguishes itself from siblings like run_dml and run_ddl by limiting scope to SELECT queries, and 'max rows enforced' adds a meaningful boundary.

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 gives clear usage context: run one SELECT query, with a row limit and a read-only role preference. It does not explicitly name alternatives or state when not to use it, but the SELECT designation and sibling names make the primary use case evident.

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