Publish a Canva email design as a draft campaign.

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds essentially nothing beyond them: it does not explain the confirm=true requirement, that the mutation is non-idempotent, or what the resulting draft state looks like. The only mild addition is the word 'draft', implying nothing is actually sent.

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?

It is a single front-loaded sentence with zero redundancy, so it is compact. But the brevity here reflects under-specification rather than disciplined conciseness; nothing about the operation's requirements is stated.

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 destructive, non-idempotent mutation with 9 parameters (including a nested body and file-based alternative) and no output schema, the description is drastically incomplete. It omits the confirm guard, the account targeting rule, and any behavioral consequences of the write.

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 only 44% across 9 parameters, including a nested payload object, yet the description explains none of them. It says nothing about the confirm guard, account label, page_id, bundle_url, campaign_id, design_token, or the payload/payload_file mutual exclusion documented only in the schema.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the alternative publish_studio_email or get_canva_design_state. The agent is left to infer usage entirely from the tool name.

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