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

Annotations already cover safety (readOnly, idempotent, non-destructive), yet the description adds substantial behavioral context: full pagination, the semantics of a paused group suppressing ad sets inside it, the precise ACTIVE definition across status/serving_statuses/serving_count, and the _truncated incompleteness warning. This is rich operational disclosure 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?

Front-loaded with the core action, then the naming caveat, then the ACTIVE/truncation semantics. Dense but each block carries distinct information an agent must have to interpret the result correctly; only minor tightening is possible.

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 single-parameter list tool with an output schema and full annotation coverage, this is complete: it covers routing, pagination, pause inheritance, active-row interpretation, and truncation, which is exactly what an agent needs to call and reason about the result.

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?

There is one parameter, account_id, at 0% schema description coverage, and the description never explains it or how it is obtained (e.g., via list_linkedin_ad_accounts). The field-level detail it does provide concerns output fields, not inputs, so parameter meaning is left to the schema/name.

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?

Specific verb+resource ('Lists ALL campaign groups in a LinkedIn ad account') with scope ('fully paginated'). It explicitly disambiguates against the sibling list_linkedin_campaigns by explaining the UI/API naming mismatch and stating this is the RIGHT tool when someone asks for LinkedIn campaigns.

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?

Gives clear when-to-use guidance tied to a real user phrasing ('when someone asks to list their LinkedIn campaigns') and explains the UI ambiguity that would otherwise route the agent wrong. It does not name list_linkedin_campaigns as the contrasting sibling, so the boundary is implied rather than fully spelled out.

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