df_create_version

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

Annotations only say readOnlyHint=false, so the description's 'WRITES TO DATAFORGE' mainly restates that, but it adds meaningful behavioral facts: content is cloned from the stated source and creation consumes the license version limit. There is no contradiction with 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?

The description is two short sentences and front-loads the mutation warning before the purpose. The only mildly redundant element is 'WRITES TO DATAFORGE,' which adds little beyond the readOnlyHint=false annotation.

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?

It captures the two behavioral essentials (clone source and license count), but with no output schema it does not describe what a successful call returns. It also leaves is_global and the exact semantics of project_id/name to inference, which is a noticeable gap for a create endpoint.

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 20%, and the description compensates only for clone_from_version by explaining the clone source and global-version default. Required params like project_id and name, plus is_global, receive no semantic help, leaving them ambiguous beyond the property names.

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 by declaring a write operation and then says 'Create a project version,' a specific verb and resource. This clearly positions it against siblings like df_update_version and df_delete_version, so an agent can identify it without opening the schema.

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 explains the clone default ('from the current global version when omitted'), which helps decide whether to pass clone_from_version, but it never says when to prefer this tool over df_update_version, df_import_version_from_git, or df_export_version_to_git. Usage context is only implied by the word 'Create.'

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