query_sql

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable context: it explicitly rejects INSERT/UPDATE/DELETE/DROP, rejects multiple statements, and documents the truncation behavior (max 100 rows). This enriches the agent's understanding beyond annotations.

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?

Well-structured with clear sections and bullet points. Front-loaded with purpose. Slightly verbose but every sentence adds essential information. No redundancy.

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?

Despite no output schema, the description thoroughly explains the return format (columns, row_count, rows, truncated). It also covers error cases (rejection of non-SELECT). For a read-only SQL tool, this is fully complete.

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?

With 0% schema description coverage, the description fully compensates by exhaustively detailing the sql parameter: it must be a single SELECT statement, standard SQL allowed constructs (JOIN, WHERE, etc.), and explicitly forbids a trailing semicolon. This leaves no ambiguity.

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 tool executes a single SELECT statement and returns results, using specific verbs and resources. It distinguishes itself from siblings (list_tables, describe_table, summarize_results) by focusing exclusively on SELECT 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?

Explicitly states when to use (SELECT only) and when not to use (non-SELECT, multiple statements). Provides clear guidance to first explore schema using list_tables and describe_table, preventing common errors.

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