Tables Clone Table

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds the meaningful behavioral fact that the clone is zero-copy (no data duplication at creation), but omits what happens on target-name collision, whether the clone is independently writable, and that repeated calls will not be idempotent.

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 no filler; the key distinguishing property appears immediately. It is arguably too terse rather than padded, so conciseness itself is strong.

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?

Output schema exists and both parameters are fully documented, so the description need not explain return values. However, for a create-style operation the description leaves out preconditions (target must not exist), source-vs-clone dependency semantics, and failure modes—context an agent needs before invoking it.

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 the schema itself documents the quoting convention for both source_table and target_table. The description adds nothing about parameters, but with full schema coverage the baseline 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?

Specific verb plus resource ("Create a zero-copy clone of an existing table") that clearly identifies the object type and the distinguishing characteristic (zero-copy) versus a plain table creation. It does not, however, differentiate itself from nearby siblings such as tables_create_table, recipes_clone_table_recipe, or the analogous schemas_clone_schema / databases_clone_database.

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?

There is no guidance on when to pick this over tables_create_table or recipes_clone_table_recipe, and no prerequisites are stated—e.g. that the target must not already exist, whether the source must be accessible, or any edition/privilege requirements. The agent must infer all selection logic from the tool name alone.

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