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

Annotations declare a non-destructive, non-idempotent write, and the description adds genuinely new behavioral context beyond that: which properties are carried over (template, sender, subject overrides, audience segment, warm-send settings) and that the result is a draft, not a sent broadcast. It omits permission requirements and what the response contains, but the added state/side-effect detail is substantive.

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?

Three short sentences are front-loaded with the action and use the remaining space for the naming convention, carried-over fields, and resulting state. No sentence is redundant and nothing is padded.

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 single-parameter duplication tool this covers action, effect, and resulting state well. The one gap is that no output schema exists and the description never says what is returned (e.g., the new broadcast's ID), which an agent needs to chain into edit/send operations.

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?

Only one parameter exists and schema description coverage is 100%, so the UUID semantics are already fully documented by the schema; the description adds no syntax, constraints, or format detail about it. The carry-over sentence describes the tool's effect rather than the parameter, so 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 first sentence states a precise verb+resource ('Create a draft copy of an existing broadcast') and is inherently distinguishable from the sibling meisa_create_broadcast, which makes new content rather than copying an existing one. It even specifies the resulting name convention ('<name> (Copy)') and the fields carried over, giving the agent an unambiguous picture of the 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?

'Useful for reusing a proven campaign' gives clear when-to-use context for a duplication tool. It stops short of being explicit about alternatives (e.g., meisa_create_broadcast for net-new campaigns) or exclusions, so it is strong context without full routing guidance.

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