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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results are windowed aggregates and paginated, which is useful, but it does not state ordering behavior, default sort, or how empty windows are handled.

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 sentences, front-loaded with the core computation and closed with the pagination trait. No filler and nothing misplaced.

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 12-parameter, read-only aggregate tool with full schema coverage, no output schema, and complete annotations, the description explains what the returned rows represent (per-domain citation percentage and average citations), which is the key missing piece absent an output schema. It omits any mention of the filtering dimensions, but those are fully documented in the schema.

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 100% across all 12 parameters, so the schema already documents dates, pagination, sort keys, and filters. The description only echoes the date window ('in the window') and pagination, adding no syntax or semantics beyond the schema. Baseline 3 applies.

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 states a specific computation: per-domain citation share (percentage of analyzed responses citing each domain) and average citations per response. This is a clear verb+resource. However, it does not distinguish itself from the crowded analytics siblings (list-source-url-analytics-tool, get-source-type-analytics-tool, list-brand-analytics-tool), which an agent could easily confuse it with.

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 or when-not-to-use guidance. With roughly a dozen sibling analytics tools that group the same underlying responses by different dimensions (source, source URL, source type, platform, prompt, brand, monitor), the description gives the agent no signal for choosing this tool over the alternatives.

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