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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the vague notion of converting a draft into a pack, with no detail on whether the source draft is consumed, what permissions are required, or what state results — minimal value beyond the 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?

A single short phrase, front-loaded with no padding, but it is terse to the point of under-specification rather than genuinely concise. The compactness is achieved by omitting needed information, not by efficient wording.

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 mutation tool with three parameters and a transformation semantic, the description is far too thin. An output schema exists so return values need not be explained, but the missing usage routing, parameter meaning, and behavioral consequences leave the definition incomplete.

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% for all three parameters, so the description carries the full burden and fails. It hints at draft_name ('launch draft') and interest_pack_name ('audience pack') implicitly, but says nothing about connection_context or how these parameters interact, leaving the agent to guess.

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 verb ('Keep') and resources ('launch draft', 'audience pack'), but the terminology is opaque — 'keep as' could mean save, convert, or materialize. It does not distinguish itself from siblings like interests_save_fetched_pack or interests_use_targets, so an agent cannot tell which tool is appropriate without opening the schema.

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?

No guidance on when to use this versus interests_save_fetched_pack, interests_save_targets, or interests_use_targets. The description offers no prerequisites, no trigger condition, and no exclusions — only what the tool nominally does.

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