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

Annotations already declare read-only, idempotent, non-destructive behavior; the description adds ordering ('newest first'), the status vocabulary, and the important data-model detail that there is no saved recipient list and audience is derived from account chats. It does not disclose pagination behavior or rate limits, so it adds useful but not exhaustive behavioral context.

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, scannable, and every clause carries operational information; the colon-delimited field list and the recipient-list caveat are efficient. The parenthetical account filter phrasing is slightly dense, but there is no filler.

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?

No output schema exists, so the description appropriately names the returned campaign fields, ordering, filters, and status values. For a read-only list tool with annotations covering safety, the main remaining gap is pagination behavior for page and per_page.

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%, so the description must carry parameter meaning. It explains account_id as tg_account_id, the account_uuid alternative, and status narrowing with enumerated values, but page and per_page are never mentioned. That leaves the pagination parameters undocumented in both schema and description.

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 opens with a specific verb and resource ('list... Telegram campaigns'), states ordering ('newest first'), enumerates returned fields, and explicitly distinguishes the recipient-list case from preview_tg_campaign_audience and list_tg_campaign_recipients. An agent can identify this as the campaign-browsing tool 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?

It gives explicit routing for audience and recipient data to two sibling tools and explains how account filtering works, but it does not explicitly say when to choose this over get_tg_campaign or how pagination should be used. This is clear context, but not a complete when/when-not guide.

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