dataset_version_create

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/non-destructive profile is covered. The description adds genuinely useful behavior beyond that: the dedupe rule that an unchanged dataset returns the existing version rather than minting a new one. No auth, quota, or return-value details, but the key non-obvious behavior is disclosed.

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?

Two tight sentences, zero filler. The creation action is front-loaded and the dedupe caveat follows immediately as the second-most important fact.

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 two-parameter creation tool with no output schema, the description covers what it does, what input forms are accepted, and the notable unchanged-dataset behavior. Without an output schema the description could have said what the returned version object looks like, which is the only remaining 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 100%, so both parameters are already documented in the schema, and the description's restatement of the accepted ref formats for 'dataset' duplicates that text. The optional 'description' note parameter is not elaborated, so this is baseline territory.

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?

States a specific verb and resource ('Create a frozen dataset version snapshot') and enumerates the accepted reference forms. It is clearly distinguished from siblings like datasets_create (dataset creation) and dataset_version_restore (rollback), so an agent can select it without opening another 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?

Gives clear context for when to call it (to snapshot a dataset) and an important conditional outcome (unchanged dataset reuses the existing version). It does not name the closest alternative, dataset_version_restore, or state when not to create a version, so it stops short of full routing guidance.

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