df_import_version_from_file

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's main contribution is the explicit overwrite behavior for target_method=replace and the on-premises constraint. The blanket 'PERMANENTLY DELETES DATA' sentence adds dramatic context but is vague about what exactly gets deleted. Still, it adds useful behavioral nuance beyond the annotations.

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?

Three short sentences with no filler; each adds a distinct piece of information. The warning is front-loaded, which is attention-grabbing but arguably overstates the tool's primary behavior. Overall it is appropriately sized, though the opening sentence could be more precise.

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 9 parameters, nested objects, and no output schema, the description is too thin. It covers only target_method and on-premises availability, omitting how file_path is used, what target_version_name must be, how conflict_strategy interacts with imports, and what the boolean options control. For a destructive import operation, this is a significant completeness gap.

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 only 33%, so the description must compensate, but it only clarifies target_method=replace. It does not explain file_path, target_version_name, conflict_strategy, encryption_password, or any of the nested options. This leaves most of the 9-parameter surface underdocumented.

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 states the specific operation: importing a version from a local .dfexport.zip archive, and distinguishes it from git-based import by noting 'local' and 'On-premises installations only.' However, the leading warning 'PERMANENTLY DELETES DATA IN DATAFORGE' is alarming and somewhat obscures the primary import purpose, though it does signal destructive potential.

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?

It provides context: on-premises only, local archive, and explains that target_method=replace overwrites. However, it does not explicitly name alternatives such as df_import_version_from_git or df_preview_import, nor state when to prefer them. The 'local .dfexport.zip archive' implies the file-based path, but the guidance is not fully explicit.

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