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

Annotations already establish that this is a safe read (readOnlyHint=true, openWorldHint=false), so the bar is lower. The description still adds real behavioral context the annotations do not: the call is free, counts always span the whole campaign even when one stage is listed, and items are ordered most-recently-active first. It stops short of describing response formatting details.

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 what the tool returns before moving to cost, ordering, and pagination instructions, and almost every clause carries information. The closing sentence about deciding what to do next is slightly generic padding but also serves as usage framing.

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?

With no output schema, the description must explain return values, and it does describe the payload shape (searches, creators per stage, next action, waiting-on party) plus count semantics. It leaves the exact field names and per-item structure implicit, which is a modest gap for a tool with four parameters and no output schema.

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 coverage is 100%, so every parameter is already documented in the schema, and the baseline is 3. The description does add one genuinely useful interaction rule beyond the schema — that paging requires stage and that limit applies per stage while counts remain campaign-wide — but it repeats the schema's own 'needs stage' pairing rather than extending it.

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 uses a specific verb and resource ('Shows where a campaign stands') and enumerates exactly what comes back: searches run plus creators grouped by stage, each with next action and who the conversation is waiting on. That detail distinguishes it from siblings like list_campaigns (which just enumerates campaigns) and get_conversation (single thread), so an agent can pick it 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 a clear decision context ('Use it to decide what to do next across a campaign') and explicit operational guidance for the pagination case: pass stage, then read page 1, 2, … until you have count items. It does not name sibling alternatives or state when not to use it, which keeps it from a 5.

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