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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral detail beyond the schema: window_days floors to discrete buckets (1/7/14/28/30/60/90) and time_zone reflects the workspace zone. However it omits notable traits for a read tool of this size — pagination via cursor/limit/retry, and especially that include_pii can return personal data.

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 tightly packed sentences with no filler; the behavioral constraints about window_days and time_zone are placed where they are needed. The first sentence is telegraphic enough to be slightly cryptic, but nothing 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?

For a 27-parameter, nested-object, no-output-schema dispatch tool, the description leaves the agent guessing about required inputs, report-type selection, pagination, and PII exposure. The two behavioral notes are useful but far short of what is needed to call this 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?

With 27 parameters and 0% schema description coverage, the description must carry the burden, and it explains only two: window_days flooring and time_zone defaulting. It says nothing about the required `report` and `workspace` params, the model vs comparison_model distinction, compare/compare_to/compare_from, cursor pagination, or include_pii 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?

The description is a keyword list of report categories (attribution, model comparison, journeys, paid media, revenue+MER, heatmaps, insights) that maps loosely to the `report` enum, but it never states a verb or explains that this single tool dispatches on the required `report` parameter. An agent must open the schema to learn what the tool actually does, and several siblings (analytics_query, attribution_journeys_get, ads_breakdowns_get) overlap without any differentiation.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives despite heavy sibling overlap with analytics_query, attribution_journeys_list, ads_breakdowns_get, and funnels_analytics_get. The agent cannot tell from the description which tool to pick for a given analytics question.

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