execute_sql

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

No annotations provided, so description carries full burden. It discloses multi-statement support (semicolon-separated), but critically omits: whether the tool returns result sets, error handling behavior, transaction semantics, timeout limits, or safety warnings appropriate for arbitrary SQL execution.

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?

Extremely concise single sentence with main action front-loaded. The parenthetical addition '(支持多条SQL语句，以分号分隔)' efficiently conveys multi-statement capability without verbosity. 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?

Inadequate for a high-complexity database execution tool with no output schema and no annotations. Missing critical context: return value format (result sets vs execution status), error handling, safety considerations for destructive operations, and whether it distinguishes between DDL/DML/DQL statements.

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% with the 'query' parameter already described as '要执行的SQL语句'. The description adds context that multiple statements are supported (semicolon-separated), which applies to this parameter, but does not elaborate on SQL syntax requirements, injection risks, or result set limits.

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?

Clearly states the tool executes SQL on MySQL databases with specific verb '执行' (execute) and resource 'SQL'. However, it does not explicitly differentiate from read-only siblings like 'get_table_desc' or 'get_table_index' that could be used for inspection instead.

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?

Provides no explicit guidance on when to use this tool versus the specialized read-only alternatives (get_table_desc, get_table_index, etc.). While it notes multi-statement support in parentheses, it lacks warnings about write operations or prerequisites like permissions.

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