execute_sql

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

No annotations provided, so description carries full burden. It mentions fallback mechanism but fails to disclose if writes are allowed, timeout behavior, error handling, or result format. For a tool executing arbitrary SQL, this is insufficient.

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?

One sentence, efficient and to the point. Could be slightly more structured with line breaks, but conveys essential info without waste.

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?

No output schema or annotations provided. Description lacks essential details like return format, error behavior, and safety warnings for a tool that can run arbitrary SQL. Incomplete for real-world 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?

Single parameter 'sql' with 100% schema description coverage. Description adds 'arbitrary SQL query' but no additional details (e.g., SQL dialect, length limits). Baseline 3 since schema already documents the parameter.

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?

Description clearly states 'Executes an arbitrary SQL query' with details on connection method (direct or RPC fallback). Distinguishes from siblings like 'apply_migration' which is for schema migrations.

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?

No explicit guidance on when to use this tool versus alternatives. Other tools like 'list_tables' or 'get_database_stats' may also run queries but no context provided. Implied use is for arbitrary SQL, but no constraints or exclusions.

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