execute_multi_sql

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

No annotations are provided, so the description carries the full burden. It discloses safe mode behavior, its default restriction of write operations, and how to disable it. It also mentions return format (list of dicts with results/errors). However, it does not detail error handling or transaction behavior, which is notable for a mutating 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 well-structured and front-loaded: a clear summary line, followed by safe mode details, then Args and Returns. Every sentence adds value without redundancy, making it efficient and easy to parse.

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?

The tool has moderate complexity (multi-query execution, safe mode). The description covers safe mode and return format. Since output schema exists, return value explanation is not required, but it's provided. Missing details like sequential execution or transaction borders, but overall sufficient for an agent to use correctly.

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?

With only one parameter and 0% schema description coverage (schema only has 'title'), the description adds meaningful detail: 'List of SQL query strings to execute'. This explains the array contents beyond the schema's type and title, meeting the need for parameter clarity.

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 tool executes multiple SQL queries against a Databend database, with a specific verb ('execute') and resource ('multiple SQL queries'). It distinguishes from sibling tool 'execute_sql' by specifying 'multiple' and mentions safe mode protection, adding context beyond the name.

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?

The description explains safe mode and how to disable it, but does not explicitly guide when to use this tool versus alternatives like 'execute_sql' for single queries. No when-not or when-to-use guidance is provided, leaving the agent to infer from context.

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