execute_sql

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

With no annotations, the description carries the full burden. It does disclose that SQL is executed unchanged and that permissions are the safety boundary, which hints at potential side effects. However, it does not explicitly warn that SQL can be mutating, nor does it describe return behavior or async execution, leaving gaps for a dangerous 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?

The description is a single, front-loaded sentence with no wasted words. It states the core purpose and a safety caveat succinctly. However, it is so brief that it under-specifies critical aspects, though that is more relevant to completeness than conciseness.

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 tool that executes arbitrary SQL, with no output schema, no annotations, and 6 undocumented parameters, this description is insufficient. It does not explain the return value, the effect of run_async or query_limit, or how this relates to sibling tools like get_sql_result. The tool is high-complexity and the description leaves many critical gaps.

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 description coverage is 0%, and the description provides no information about any of the 6 parameters (database_id, sql, schema, catalog, run_async, query_limit). The agent gets no help understanding what these parameters mean or how to use them, so the description fails to compensate for the schema's lack of descriptions.

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 action ('Execute SQL') and the specific context ('through SQL Lab'), distinguishing it from sibling tools like get_sql_result or get_query. It is specific and unambiguous.

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 guidance is provided on when to use this tool versus alternatives such as get_sql_result or get_query. The safety-boundary remark is a caution, not a usage guideline, and no exclusions or alternative references are mentioned.

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