preview_twb_migration

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool is for 'preview,' implying a read-only or simulation action, but does not clarify if it requires specific permissions, what the preview output entails (e.g., report format), or any side effects like temporary file changes. This leaves significant gaps for a tool with multiple parameters.

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 a single, clear sentence with no wasted words, making it easy to parse. It is front-loaded with the core action, though this brevity contributes to gaps in other dimensions like guidelines and transparency.

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 tool has 4 parameters, 0% schema coverage, no annotations, but an output schema exists, the description is minimally adequate. It states the purpose but lacks details on parameter usage, behavioral context, and differentiation from siblings. The output schema may cover return values, but the description does not fully address the tool's complexity.

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%, meaning parameters are undocumented in the schema. The description adds minimal semantics by mentioning 'workbook migration' and 'target datasource,' which loosely relate to 'file_path' and 'target_source,' but does not explain 'scope' or 'mapping_overrides' or provide usage examples. It fails to compensate for the low schema coverage.

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 action ('preview a workbook migration') and the target ('onto a target datasource'), which is specific and actionable. However, it does not explicitly differentiate from sibling tools like 'apply_twb_migration' or 'migrate_twb_guided', which might handle actual migrations, so it lacks sibling distinction.

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 no guidance on when to use this tool versus alternatives, such as 'apply_twb_migration' for executing the migration or 'profile_twb_for_migration' for analysis. It also omits prerequisites, like needing a valid workbook file or target source, leaving usage context unclear.

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