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 genuine value beyond that: it notes that visitor signals are distinct and hashed, and that placements served versus browser-measured viewable impressions are separate measures — a non-obvious data caveat.

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?

Purpose and scope are front-loaded, followed by a dense but information-rich inventory of metrics. It is longer than a one-liner but each clause describes a distinct returned data point, so little 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?

There is no output schema, yet the description thoroughly enumerates the return contents (views windows, visitor signals, clicks, leads, funnel, locations, per-listing views). For a read-only tool with one optional parameter, an agent has everything needed to invoke and interpret it correctly.

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 the single 'listing' parameter is fully documented in the schema, including the omit-for-all behavior. The description adds no extra parameter syntax or format detail, so the baseline 3 is appropriate.

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 pairs a specific verb ('Read'/'get') with a precise resource ('audience analytics for the user's own listings') and enumerates the exact metrics returned. It is clearly distinguishable from every sibling, none of which deal with analytics.

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 establishes scope — analytics for the user's OWN listings, matching the Dashboard view — which tells the agent when this tool applies. However, it names no exclusions or alternative tools (there are none among siblings), so it stops short of explicit when-not guidance.

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