Schemas Clone Schema

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

With annotations already declaring readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, the bar is lower, and 'zero-copy' does add real value by signaling a metadata-only operation with no data duplication. However, the description says nothing about failure when the target already exists (consistent with the non-idempotent hint), permission requirements, or what storage the clone inherits.

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 wasted words. It is efficient, though its terseness borders on under-specification for a mutating operation.

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?

The rich structured data (full schema coverage, an output schema, and four annotations) carries most of the load, so the thin description is not fatal. Still, for a schema-mutating clone the description omits when to use it, the target-must-not-exist precondition, and cross-database behavior.

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 the schema already documents database, source_schema and target_schema including the quoting convention, which sets the baseline at 3. The description adds no further detail on what a target_schema name means for the clone or whether the database parameter scopes both source and target.

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 uses a specific verb ('Create') with a specific resource ('a zero-copy clone of a schema'), which clearly separates it from schemas_create_schema, schemas_drop_schema, and the sibling clone tools like tables_clone_table. It does not explicitly name a sibling to differentiate, 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?

There is no guidance on when to use this versus schemas_create_schema (fresh empty schema) or databases_clone_database, and no prerequisites such as whether the target schema must be absent. The agent must infer the usage context entirely.

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