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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that, the description adds real value: the upstream endpoint (GET /api/v2/campaigns/{id}/review), the fact that a shareable `reviewUrl` is produced, and the shape of what a section contains (status, round, previous fix notes). Pagination and rate-limit behavior are not mentioned.

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?

Two compact blocks: the content payload first, then the share hint and endpoint note. It is dense and a bit run-on in the enumeration, but no sentence is wasted and the most important framing (what comes back) leads.

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 carries the return-value burden and does so thoroughly by enumerating piece fields (preview URLs, caption, labels, bookings, QA checks) and section fields (status, round, fix notes). For a three-parameter read tool this is close to sufficient; only pagination and scope limits are unaddressed.

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 100%, so all three parameters are already documented, which sets the baseline at 3. The description reinforces the main content (pieces and their bookings/QA checks) but does not clarify the `pieces=false` reduction or `sectionId` scoping beyond what the schema already says.

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 states the resource precisely: a campaign's pieces grouped into review sections, and enumerates the grouping kinds (episode, week, channel set, variant group, creator's own). It is clearly a read/fetch tool, distinguishable from siblings like decide_campaign_review_section or group_campaign_review, though it never opens with an explicit verb like 'Retrieve'.

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?

Usage is implied rather than stated: the note about sharing `reviewUrl` so a person can preview and decide suggests this is the fetch step before deciding, but no sibling is named as an alternative and there is no explicit when/when-not guidance. An agent can infer the workflow but must infer it.

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