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. The description adds real behavioral context beyond that: results are filtered to actively tracked advertisers, saving an ad does not bypass tracking limits, and ad_id reverses the lookup to report list membership.

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?

Three dense sentences, front-loaded with the resource and scope, then parameter behavior. No filler, though the ad_id clause is slightly convoluted and the 'saving an ad does not bypass tracking limits' line sits oddly at the end.

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 two-optional-parameter read tool with no output schema and full annotation coverage, the description covers both parameters, the precedence rule, and the tracking-scope caveat. The one material omission is the zero-argument behavior, which an agent will likely hit given no required parameters.

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 carries the full burden and mostly does: list_id selects one owned list, ad_id reports which of your lists contain that internal ad ID, and precedence is stated when both are supplied. The gap is the case where neither is supplied (both are optional), whose default behavior is never described.

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 ('Read your saved lists') and adds the defining scope condition that ad creatives are limited to actively tracked advertisers. This distinguishes it from generic list/ad tools among the siblings, though it never names an alternative 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?

It explains how to choose between the two parameters (ad_id takes precedence over list_id), which is useful in-call guidance. But it gives no guidance on when to use this tool versus siblings like get_projects or list_brand_ads, and no exclusions or prerequisites.

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