execute_mutation

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

With no annotations, description should disclose safety and effects. Only mentions 'confirmed write or destructive', but lacks detail on success/failure conditions, rollback, or data loss risks.

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?

Single sentence is concise but at the cost of omitted critical information. Not well-structured for quick comprehension of tool behavior.

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?

Despite having 3 required parameters and a destructive action, the description fails to cover prerequisites, return values, or error handling. Output schema existence does not compensate for missing behavioral context.

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 0%, so description must explain parameters. It does not describe 'connection_name', 'sql', or 'confirmation_token', leaving agents to infer meaning.

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?

Description clearly states it executes a confirmed write or destructive SQL statement, distinguishing it from sibling tools like 'query' (reads) and 'preview_mutation' (preview).

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 on when to use this tool versus alternatives like 'preview_mutation' or 'query'. Missing explicit instructions for confirmation flow.

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