transfer_table

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

With no annotations, the description carries the transparency burden, disclosing the specific SQL command, the rejection of unsupported endpoints, permission drops, and the need to refresh dependent objects—though it omits details on index/statistics handling.

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?

The description is front-loaded with the purpose, followed by constraints, cautions, and parameter details—every sentence adds value with no redundancy.

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?

Given the complexity (4 required params, no annotations), the description covers key aspects like purpose, constraints, and parameter examples, though it doesn't explicitly mention prerequisite checks like schema/table existence or output details (but output schema exists).

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%, but the description provides clear explanations for all four parameters, including examples and the constraint on 'item' for SQL Analytics Endpoints, fully compensating for the lack of schema descriptions.

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 clearly states the tool moves a SQL table to another schema using ALTER SCHEMA ... TRANSFER, distinguishing it from siblings like rename_table, clone_table, or transfer_view.

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?

The description specifies it is Data-Warehouse-only and rejects SQL Analytics Endpoints, but does not explicitly contrast with other table operations like rename_table for schema changes or create_table+insert for copying.

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