run_select_query

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

With no annotations, the description fully discloses read-only enforcement (two layers), max_rows default and hard cap, and the 'truncated' field in the response. Nothing hidden.

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?

Front-loaded purpose, then details, no redundant text. Every sentence adds value. Efficiently conveys critical behavior.

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 all essential aspects for a 2-parameter tool with output schema: what queries are allowed, safety measures, result limits, and response field. Complete for effective use.

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 significant meaning beyond the schema: clarifies query must be read-only, lists allowed commands, documents max_rows default and hard cap. Compensates for 0% schema 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?

Clearly states the tool runs read-only SQL queries against ClickHouse, specifying allowed statement types (SELECT/SHOW/DESCRIBE/EXISTS). Differentiates from sibling tools that handle specific metadata queries.

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?

Details result caps and data-modifying statement rejection, but does not explicitly compare to siblings for when to use this vs describe_table, etc. The purpose is clear enough for most agents.

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