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

Beyond the annotations, the description discloses dual return modes (awaiting_approval with review_url vs. queued/suppressed counts), the approval workflow, and the multi-call behavior ('Safe to call again; it never re-sends'). This is rich context that the annotations alone do not provide. No contradiction with readOnlyHint=false, openWorldHint=true, or 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?

The description is front-loaded with purpose and mode differences, and every sentence addresses a real concern for a high-stakes send operation. It is slightly long and repeats the approval caution, but nothing is wasted.

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?

Given the complexity (real email sending, approval flows) and the absence of an output schema, the description is complete: it explains both possible outcomes, what to do with each, and the safety constraint. An agent has everything needed to call and follow up 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?

The schema has 100% coverage for the single parameter 'campaign_id', including its own description. The tool description adds no additional syntax, format, or meaning beyond what the schema already states, so the baseline 3 is appropriate.

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 description names a specific action ('Queue a campaign's reviewed contacts for sending') and distinguishes two operational modes (RankParse inbox approval vs. direct queueing). An agent can tell this is the launch/send tool, not a status or configuration tool.

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?

It gives explicit when-to-use guidance ('only call it after the user has seen the drafted emails and explicitly approved sending'), when-not-to-use ('If status is approved, it is already approved; do not launch again'), and what to do with the returned review_url. No alternative tool is named, but the conditional logic is thorough enough to route correctly.

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