run_query

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

With no annotations provided, the description fully discloses the key behavioral trait: read-only by default, with a configurable write mode. This adds essential information about side effects and authorization beyond what the schema offers.

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, front-loaded sentence that instantly conveys purpose and a critical behavioral caveat. No redundant or extraneous text.

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 description covers the tool's primary function and safety characteristic, but given the presence of an output schema (not shown) and 3 parameters with 0% schema description coverage, more parameter details would improve completeness. It is adequate but not thorough.

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%, but the description hints at 'host:port' parameters. However, it does not explain the 'query' parameter or elaborate on any parameter formats or constraints, leaving the agent with insufficient guidance beyond parameter names.

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 ('Execute SQL') and identifies the resource ('ClickHouse datasource (host:port)'). It clearly distinguishes from sibling tools like 'list_registered_datasources' and 'list_tables', which are for metadata, not query execution.

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 states the tool is for running SQL on ClickHouse, and notes that writes require a specific environment variable. This provides clear context for when to use it, though it does not explicitly exclude scenarios or mention alternatives beyond the sibling list.

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