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

Annotations already declare readOnly/no-destructive, so safety is covered; the description adds real value beyond that by describing the payload (six email stages, generation/error and pause/send state) and a non-obvious caveat that a queued acknowledgement is not completion. The only weakness is that it instructs verification via next_offset and is_regenerating, fields that appear nowhere in the schema, leaving the agent unsure how to inspect them.

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?

Four compact sentences, front-loaded with purpose then payload then paging then a caveat; no filler. The next_offset/offset phrasing is the one spot that costs clarity rather than saving space.

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?

There is no output schema, so the description rightly explains the return shape and paging state, and it flags the queued-acknowledgement pitfall. It is nearly complete for a read tool, though the unexplained limit parameter and the unreferenced next_offset/is_regenerating fields leave small gaps.

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 0% schema description coverage the description must carry parameter meaning, and it does explain entity_id (specific draft) and offset (paging). However 'use next_offset as offset' is confusing phrasing for a parameter literally named offset, and limit plus campaign_id receive no explanation at all.

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 opening sentence gives a specific verb (Read) and resource (saved drafts) and scopes it across campaign types including podcast campaigns. It implicitly separates itself from the preview-oriented sibling by emphasizing *saved* content, but never names get_campaign_draft_previews, so an agent must infer the boundary.

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 concrete retrieval guidance: 'use next_offset as offset for the next page' and 'use entity_id for a specific draft', covering both list-paging and single-draft modes. It stops short of stating when to prefer this over draft previews or get_campaign alternatives, which is the main missing piece.

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