insert

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

With no annotations, the description must disclose behavioral traits, but it only restates the tool's core function. It does not mention whether the operation is safe/unsafe, whether it returns results, errors, or side effects, or any permission requirements. This is a minimal restatement rather than meaningful behavioral disclosure.

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 concise sentence that front-loads the main action and purpose. While it is very short, it contains no wasted words, though it could benefit from additional context as noted in other dimensions.

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 1-parameter tool with good schema coverage, the description is functional but incomplete. It fails to clarify how this tool differs from the sibling 'execute' tool, nor does it describe return behavior or side effects, creating ambiguity that could lead to incorrect tool selection.

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 already includes a full description for the only parameter (sql), achieving 100% schema description coverage. The tool description adds no additional parameter semantics beyond what the schema provides, so the baseline score of 3 applies.

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 identifies the tool as executing INSERT statements to add new data to tables, using a specific verb ('执行'/'execute') and resource ('INSERT 语句'/'INSERT statement'). This distinguishes it from sibling tools like query, update, and delete, which handle other types of SQL operations.

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 the generic 'execute' tool or 'execute_ddl'. The description does not mention exclusions, prerequisites, or alternative tools, leaving the agent to infer the appropriate context from the name alone.

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