production.animation_duplicate_action

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

Annotations already declare a non-destructive, non-idempotent, non-read-only mutation, so safety is partly covered. The description adds real value by disclosing that a checkpoint is taken and an exact original-content check runs, plus the dry-run default — but 'exact original-content check' is vague about whether it verifies or aborts, and no permission or failure behavior is described.

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 compact clauses with the non-overwrite guarantee front-loaded and the dry-run instruction last. The telegraphic fragment style ('checkpoint and exact original-content check') is dense but slightly cryptic.

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 is a 6-parameter mutation tool with zero schema descriptions, and only one parameter's semantics are addressed. The output schema covers return values, but an agent still cannot tell what action_name versus name should contain or what assign does.

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%, so the description carries the full burden, yet it explains only dry_run's effect. The critical parameters — action_name (source), name (new name), assign, object_name, and operation_id — are entirely undocumented anywhere.

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 verb 'Duplicate' is specific and the 'without overwriting' clause adds a meaningful scoping constraint that distinguishes this from a plain copy. However, the resource is only inferable from the tool name (animation action), and it never explicitly contrasts itself with close siblings like animation_create_action or animation_restore_action.

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 gives one concrete operational instruction, 'Set dry_run=false to create,' which tells the agent that the default call is a no-op preview. It does not say when to duplicate versus create a fresh action or restore a checkpoint, so the choice among siblings remains implied.

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