transfer_table

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

With no annotations, the description carries the full burden and does it well: it discloses engine limitations, rejection of SQL Analytics Endpoints, dropped direct permissions, and that dependent views/procedures may need refreshing. These are material side effects an agent must know before invoking.

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 well-structured and front-loaded, with a concise operation statement followed by caveats and a clear Args section. Every sentence adds value; the repeated SQL Analytics Endpoint warning is relevant to both the operation and the parameter.

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?

For a mutating tool with no annotations, the description is remarkably complete: it covers the operation semantics, unsupported environments, permission side effects, dependency implications, and all parameter meanings. Nothing essential is missing.

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 0%, but the description compensates fully by explaining all four parameters: workspace, item, qualified_name, and target_schema, including concrete examples like 'dbo.sales' and 'archive', plus the rejection semantics for item.

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 opens with a specific verb and resource: 'Move a SQL table to another schema via ALTER SCHEMA ... TRANSFER OBJECT::...'. This clearly states what the tool does and inherently distinguishes it from sibling tools like transfer_view and transfer_procedure.

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 provides clear context and exclusions: it is Data-Warehouse-only, and SQL Analytics Endpoints are rejected. It does not explicitly name sibling alternatives for views/procedures, but the table-specific framing makes the intended use case clear.

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