execute_sql

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

No annotations provided; description discloses dangerous behavior ('full bypass of RLS', 'use with care') but lacks details on return format, transaction handling, or auth requirements.

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?

Single sentence with two clear parts: what it does and a warning. No wasted 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?

Lacks essential details about return values, error handling, and does not fully differentiate from numerous SQL-related siblings, despite the tool's high complexity.

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 100% and description adds no extra meaning beyond what schema already provides for both parameters.

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 explicitly states 'Run any SQL statement' with examples, and mentions 'full bypass of RLS' which distinguishes it from sibling tools like execute_rls_sql.

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?

Implies usage for cases needing RLS bypass via 'full bypass of RLS', but no explicit when-to-use vs alternatives like execute_rls_sql or query_db.

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