database_execute_script

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 that the tool executes a script and requires an active connection, but it does not mention side effects, return values, transaction handling, or error behavior—important for an execution 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?

A single, front-loaded sentence conveys the essential action, resource, and context without any filler or redundant restatement of the tool name.

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 simple one-parameter tool, the description covers purpose and prerequisite. However, with no output schema and no annotations, it omits expected return values and side-effect details, leaving notable gaps for an execution tool.

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?

The schema only says the 'script' is a 'SQL script to execute'. The description adds valuable semantics: it is a multi-statement script, and it runs on the active database connection. This goes beyond the schema and helps the agent understand the parameter's role.

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 uses a specific verb ('Execute') and names the resource ('SQL script') while adding scope ('multiple statements', 'active database connection'). It is close to distinguishing from siblings, but 'database_execute_batch' likely overlaps on multi-statement execution, so differentiation is not fully explicit.

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 phrase 'on the active database connection' implies a prerequisite, and 'multiple statements' hints at the intended use case. However, it does not explicitly state when to prefer this tool over database_execute_sql or database_execute_batch.

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