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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no mention of pagination via cursor, the 200-row limit cap, the 365-day window, default sort, or what the two modes return differently.

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?

A single dense sentence with no waste, but it front-loads a slash-delimited compound that reads as under-specification rather than efficient structure. It is short without being clarifying.

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 14-parameter, nested-object, multi-mode query tool with no output schema, one sentence is far from sufficient. The agent has no way to know valid entity values, field names for dimensions/measures, filter operator behavior, or defaults.

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?

All 14 parameters have 0% schema description coverage, and the description contributes no parameter meaning at all — nothing about workspace, date_range vs. days, describe, dimensions, measures, time_bucket, filters, select, or cursor. With nested objects like filters/measures/sort/time_bucket entirely undocumented in both places, the agent must guess semantics.

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?

It names two modes (list/describe entities vs. query dashboard data) and scopes the data domains to store/ads/funnels/pages/creatives, which is more than a tautology. But it never explains how the two modes relate or how this differs from siblings like analytics_report, ads_performance_get, ads_breakdowns_get, or funnels_analytics_get, all of which plausibly overlap.

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?

No guidance on when to pick this over analytics_report or the domain-specific *_get tools. It also never explains the describe=true mode, when to supply measures/dimensions versus a bare entity listing, or that workspace is mandatory.

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