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

Annotations already cover read-only, non-destructive, closed-world behavior, so the description's main added value is behavioral: results are ordered largest first and include a count from the preceding window. It does not explain pagination, filtering behavior, or auth/project scoping beyond what the schema minimally states.

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?

It is short and front-loaded: the first sentence states the core action, and the second clarifies ranking and count. The phrasing 'with the count in the window before' is slightly awkward, but there is little wasted text.

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 nested-parameter analytics query with no output schema, the description is incomplete. It says what is ranked and ordered, but omits filter semantics, limit behavior, auth/project scoping, and enough return-value detail for an agent to call it confidently.

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?

The description mentions a time window, which maps loosely to the range parameter, but it does not explain limit, channel, or projectId semantics. With schema description coverage reported as 0%, the description does not compensate for the nested request object's undocumented parameters.

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 verb and resource: getting policy labels that flagged the most content. It also specifies ordering (largest first) and count context, which distinguishes it from analytics siblings like analytics-authors, analytics-channels, and analytics-volumes.

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?

The description implies this is the analytics tool for flagged policies, but it gives no explicit when-to-use guidance, no exclusions, and no comparison to sibling analytics tools. An agent must infer selection from the resource name alone.

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