run_select

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

With no annotations provided, the description carries the full burden. 'Validated read-only' conveys that the tool will not mutate data and will validate the query, which is useful. However, it does not disclose what validation entails, potential error behavior, or return format, leaving gaps in transparency.

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?

The description is a single, tight sentence with no filler. Both qualifiers ('validated' and 'read-only') add meaningful behavioral information, making it concise and effectively front-loaded.

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 one-parameter tool with no annotations or output schema, the description offers the essential 'this is a SELECT' context, but it lacks guidance on when to choose it over the numerous sibling lookup/search tools, and does not cover expected output or validation limits. The agent is left with significant ambiguity for correct usage.

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?

The schema has a single 'sql' parameter with 0% description coverage, so the description must compensate. 'Run a validated read-only SELECT' clarifies that the parameter must contain a SELECT statement, which adds meaning beyond just 'string'. Yet it provides no further details on allowed syntax or formatting.

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 ('Run') and resource ('a validated read-only SELECT'), making it immediately clear that this tool executes SQL SELECT statements. It effectively distinguishes itself from the sibling tools, none of which mention SQL or direct 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 gives no explicit guidance on when to use this tool versus the many lookup/search siblings. It only implies through the word 'SELECT' that it is for SQL queries, but does not state conditions, exclusions, or alternatives.

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