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

No annotations are provided, so the description carries full burden. It discloses that it returns only aggregate counts and details for problematic ads, and healthy ads appear only in counts. This is a key behavioral trait. It doesn't explicitly state read-only nature, but it's implied by 'check'.

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 efficient sentences: the first states the core function, the second adds the crucial NOT distinction and routes to the alternative. Zero waste, front-loaded.

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?

Since there is no output schema, the description explains the return shape ('aggregate counts by review status and details for problematic ads only'). Covers the necessary output, the parameter nuance, and the alternative, making it complete for correct invocation.

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% and both parameters are already described. The description only reinforces the include_paused meaning ('optionally paused'), adding no new semantic detail beyond the schema.

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?

Clearly states the verb 'check', the resource 'review and policy status of ads', and the scope 'all active (optionally paused) ads in an account'. It distinguishes itself from adsap_list_ads by explicitly stating it's NOT an ad listing.

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?

Provides explicit usage context ('useful in audits to surface policy violations') and an explicit exclusion ('NOT an ad listing') with a named alternative (adsap_list_ads) for enumerating ads.

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