Databases Clone Database

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

The annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and non-idempotency. The description's 'zero-copy' adds real value by explaining that no data is physically copied at creation and the target diverges only on later writes — a trait not captured in annotations. It still omits the failure mode of an existing target and required privileges.

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 with zero filler; the key qualifier ('zero-copy') comes early. Nothing is redundant or buried.

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?

An output schema exists, so return values needn't be described, and the params are fully documented by the schema. However, for a non-idempotent mutation tool the description should mention that the target database must not already exist and that the clone requires source privileges — omissions that affect whether a call succeeds.

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% and both parameters are required strings with quoting guidance already in the schema. The description adds nothing beyond what the schema states, so the baseline 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?

States a specific verb and resource ('Create a zero-copy clone of a database'), and 'zero-copy' signals the Snowflake-specific semantics that separate this from databases_create_database. It doesn't name the sibling it substitutes for, but the operation is unambiguous.

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 when-to-use guidance at all: nothing about when to clone vs. create, whether the target must be empty/nonexistent, or what privileges (CREATE DATABASE on the source) are needed. The agent must infer all preconditions.

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