run_query

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

Given no annotations, the description reveals read-only behavior, query type restrictions, and automatic LIMIT. It does not cover error handling or response format, but core behaviors 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 concise sentences: first states purpose, second adds constraints. No superfluous words, front-loaded structure.

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?

With low complexity (1 param) and an output schema present, the description covers essential context: target table, read-only, and query limitations. Minor gaps like error handling are acceptable.

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 coverage is 0%, so description must compensate. It adds context by specifying the target table and query constraints, which adds meaning beyond the bare parameter name.

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 clearly states the verb 'Run a READ-ONLY SQL query' and the specific resource 'samples.nyctaxi.trips', with explicit read-only nature and allowed query types. This fully defines the tool's purpose.

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?

It provides constraints like 'Only a single SELECT/WITH is allowed' and 'LIMIT 1000 is appended if missing', guiding usage. No alternatives are discussed, but no siblings exist, so it's adequate.

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