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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that returned records carry status and bidding config, which is useful since there is no output schema, but says nothing about page-size behavior, cursor semantics, or whether results are complete without paging.

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?

A single front-loaded sentence with no filler; the resource, its parent scope, and the returned fields are all in the first clause set. Nothing is wasted.

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 read-only list tool with full schema coverage and no output schema, the description gives enough to call it correctly and hints at return contents. The only gap is that pagination and result-set behavior are left entirely to the 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 description coverage is 100%, so all six parameters are documented in the schema itself, and the description only restates the campaign scoping. No added meaning beyond the schema (e.g., expected ID formats or cursor reuse rules), so the baseline 3 applies.

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?

States a specific verb and resource ('List ad groups') plus the scoping parent ('belonging to a ChatGPT Ads campaign') and the payload hints ('status and bidding config'). This distinguishes it in practice from list-openai-ads-ads and list-openai-ads-campaigns, though it never names those siblings explicitly.

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?

No guidance on when to use this versus get-openai-ads-ad-group (single item) or list-openai-ads-ads (child ads), and no mention of pagination workflow despite two cursor parameters. Usage is only inferrable from the phrase 'belonging to a campaign'.

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