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

With no annotations, the description carries the full burden and does so well: it discloses the live triple-window fetch, the performance cost, the paging model, and warns that conclusions drawn from a truncated slice are wrong. It omits auth/permission needs, but for a read analysis tool that is minor.

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 is front-loaded, then the cost warning, then a clearly-labeled PAGING block. It is slightly long-winded in the pagination explanation, but every sentence informs correct invocation rather than padding.

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?

No output schema exists, so the description must explain return shape; it does so by naming the pagination fields (returned, total_available, truncated, next_offset) and interpreting truncated. Combined with the schema's parameter docs, an agent has enough to call and page correctly, with the missing site_id definition the main gap.

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 75% and documents limit/offset/min_clicks defaults. The description adds meaning by explaining the pagination contract (next_offset, raising limit) and how totals relate to paged rows, which the schema alone does not convey. site_id remains 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+resource: identifies pages whose clicks fall across both of two consecutive 30-day windows, explicitly excluding single-period drops. This distinguishes it conceptually from siblings like Live_Traffic_Drops, though no sibling is named. The 'three-window slide' framing is concrete and unambiguous.

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?

Offers a caution ('slowest tool in this module; run it sparingly'), which is real usage guidance about cost. However, it never says when to prefer this over alternatives such as Live_Traffic_Drops or Live_Quick_Wins, leaving tool selection to inference.

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