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

No annotations exist, so the description carries the full burden. It partially earns this by disclosing a dependency on the product's connected publisher token, which signals a likely failure/empty-result mode when unconnected. It says nothing about pagination, result limits, ordering, or error behavior.

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?

One sentence with no filler, and the resource is front-loaded before the scoping clause. It is efficient, though the terseness contributes to the parameter and usage gaps rather than resolving them.

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?

The tool is low complexity (one required param, no output schema, no nesting), and the description conveys the result set's scope. Still, with no annotations, no output schema, and 0% schema description coverage, the description leaves the parameter and the returned/failure behavior entirely unexplained.

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% for the single parameter product_id, so the description must compensate but does not. It only alludes to 'this product' without defining what a product_id is, its format, or where it comes from, leaving the sole parameter undocumented in both places.

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 the Audience Resolver projects') with a scope qualifier ('reachable by this product's connected publisher token'). This distinguishes it reasonably from the sibling list_audience_resolver_calendars, though it does not name the sibling explicitly or explain the difference in scope.

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?

The phrase 'reachable by this product's connected publisher token' implies a prerequisite (a connected Audience Resolver token for the given product), which hints at when the tool is usable. However, it never states when to use this versus connect_audience_resolver or list_audience_resolver_calendars, and there are no explicit exclusions.

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