query

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

Discloses auto-appended LIMIT for SELECT/WITH queries and mentions the read-only nature. No annotations are provided, but the description adds significant behavioral context without contradictions.

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?

Three sentences, each serving a purpose: stating function, explaining auto-limit, and providing usage guidance. No redundant words.

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 single-parameter SQL query tool without output schema, the description covers purpose, allowed operations, automatic behavior, best practice, and alternative tool, making it fully informative.

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 covers 100% of the parameter, but the description adds guidance on allowed statement types and query best practices, enhancing the schema's basic description.

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 executes read-only SQL queries, listing specific statement types (SELECT, SHOW, DESCRIBE, EXPLAIN) and distinguishes itself from the sibling 'execute' tool for data modification.

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?

Explicitly states when to use (read-only queries) and when not (data modification), and provides a best practice to prefer specific columns over SELECT * to reduce response size.

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