mutation_preview

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

No annotations present, but the description clearly states the tool is non-executing, shows estimates and samples, and mentions parameter limits (sampleSize max 20). Does not detail error handling but adequate for a preview 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?

Three concise sentences that front-load purpose, then provide usage guidance and parameter hints. No fluff or repetition.

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?

All five parameters are covered by schema and description. Output behavior (estimated rows and samples) is described. Lacks description of error cases, but tool complexity is low and no output schema is expected.

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 description coverage is 100%, so baseline 3. The description adds minor reinforcement for optional overrides, but no significant extra meaning beyond the schema.

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 'preview the effect of INSERT/UPDATE/DELETE without executing' with specific verb and resource, and distinguishes from siblings like execute_sql which actually run queries.

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?

Explicitly advises using this 'before running destructive queries to verify the impact', and describes optional server/database/schema overrides. Lacks explicit 'when not to use' but context implies distinction from actual execution.

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