Publish a Studio email export as a draft campaign.

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=false. The description adds only 'draft campaign,' which hints that publishing does not immediately send, but it omits critical behavioral context such as the confirm=true requirement, account profile constraints, and payload mixing rules.

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 single sentence is front-loaded and contains no wasted words, but it is essentially a verbatim restatement of the title and therefore does not use the space to convey needed operational detail.

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 an 8-parameter, nested-payload, destructive, open-world mutation tool with no output schema, the description is far too thin. Annotations cover the safety profile, but the description omits parameter guidance, usage conditions, and any operational constraints an agent needs to invoke it correctly.

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?

With 8 parameters and only 50% schema description coverage, the description compensates for nothing. It never mentions html, title, account, confirm, payload, asset_id, campaign_id, or payload_file, leaving critical parameters like the confirm requirement entirely absent from the natural-language guidance.

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?

Tautological: description restates name/title.

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?

Provides no when-to-use or when-not-to-use guidance. The existence of publish_canva_email is not referenced, and no prerequisites or context for selecting this tool over alternatives are given.

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