Duplicate a form

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing that the operation changes community state and requires confirm=true, an operational gate not visible in 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?

Two short sentences with the action stated first and the state-change/confirmation requirement immediately after. Nothing is padded or redundant.

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 form-duplication tool with full annotation coverage and no output schema, the definition gives the agent enough to call it correctly, including the confirmation gate. It stops short of describing what the duplicate inherits (settings, submissions, naming), which would be useful but is not strictly required to invoke it.

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%, including a note that 'account' selects credentials rather than a remote ID, so the schema does the heavy lifting. The description only reinforces the confirm semantics already documented in the schema, adding no new parameter detail — baseline 3 applies.

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 a specific verb and resource ('Duplicate a form'), which cleanly separates it from create_form, update_form, and delete_form. It doesn't need to name a sibling explicitly because the resource noun does the differentiating within a large duplicate_* family already present in the toolset.

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 confirm=true clause implies this is a user-requested action, but there is no explicit when-to-use guidance relative to create_form (e.g., 'use this instead of recreating a form manually') and no stated prerequisites beyond confirmation. Usage is inferable but not spelled out.

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