run_query

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

No annotations provided, so description carries full burden. It declares the tool as read-only and non-destructive, explains server-side row cap (default 500), and optional column filtering. Does not cover error handling or authorization, but adequate for a query tool.

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?

Description is a single focused paragraph. Front-loaded with purpose, then parameter details. Every sentence adds value; no fluff. Efficiently communicates key syntax constraints and usage tips.

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?

Given 4 parameters, no output schema, and no annotations, the description covers essential aspects: purpose, parameter semantics, return format, and Firebird-specific syntax. Minor gaps: no mention of error outcomes or what happens when maxRows is exceeded, but still complete for practical use.

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 add meaning. It explains that 'database' key comes from list_databases, 'sql' must be Firebird-compliant SELECT, 'maxRows' is a server-side cap defaulting to 500, and 'columns' reduces noise. All parameters are clearly described beyond type/default.

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 'Execute a read-only SELECT query', specifying both the verb and resource. It distinguishes from sibling tools like execute_dml and execute_ddl by emphasizing read-only nature and SELECT syntax. The return format is also described.

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 instructs to use Firebird-specific row limiting syntax ('SELECT FIRST n' or 'ROWS n') and warns against 'LIMIT n'. Mentions maxRows and columns for result control. Could be improved by explicitly stating when to use alternative tools (e.g., DML or script execution).

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