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

Goes well beyond the annotations: it clarifies the original is NOT changed, that references, generations and refine chat are NOT copied, that nothing is published, and that the return includes the new card and a duplicatedFromId along with a url. These are exactly the mutation-boundary facts an agent needs and are not derivable from readOnlyHint=false / destructiveHint=false.

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?

A single tightly packed passage with the action and the scoping constraints front-loaded; every clause (placement, no date, nothing published, return shape) carries information the agent needs. No filler.

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 mutation with no output schema, the description supplies the behavioral envelope and the return shape (new card, duplicatedFromId, url), which is close to sufficient. It stops short of describing error conditions, required permissions, or what contentId/brandId must refer to.

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% and the description adds no meaning for contentId or brandId, nor does it clarify the relationship between them or whether brandId is optional. It lists the fields that get duplicated, which is useful context, but says nothing about the two actual parameters.

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 copy of a content card') and enumerates the copied fields plus where the copy lands (bottom of the idea column, no planned date). It implies the distinction from create_content by specifying a copy of an existing card, but never names that sibling explicitly to make the routing unambiguous.

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?

Usage is implied by the detailed statement of what is and is not copied, so an agent can infer this is for cloning an existing card rather than authoring new content. However, there is no explicit when-to-use/when-not guidance and no alternative tool is named, leaving the agent to infer the choice between this and create_content or bulk_create_contents.

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