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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the useful behavioral detail that output is bucketed time-series data capped to top_n URLs (default 20, max 50), but says nothing about the required interval granularity or result shape.

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 tight sentences that front-load the metric definition before the cap constraint. No filler, though the second sentence largely duplicates schema content already stated in top_n's description.

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 9-parameter, time-series analytics tool with no output schema, the description covers the metric and the cap but omits the bucketing/interval requirement, sibling differentiation, and any note on filters (tags, monitors, countries, platforms). Annotations carry the safety profile, but the functional description is thinner than the tool's complexity warrants.

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%, so the schema already documents all 9 parameters including top_n's default/max and interval's allowed values. The description only restates the top_n cap, adding no meaning beyond the schema, so the baseline 3 is appropriate.

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 names a specific metric ('percentage of analyzed responses that cited that exact URL') per top URL over time buckets, which is a clear verb+resource definition. However, it does not distinguish itself from close siblings like get-source-usage-time-series-tool or get-source-url-type-analytics-tool, so an agent must infer the boundary.

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 explicit when-to-use guidance, no conditions that select this tool over the many sibling time-series/analytics tools, and no note that interval is required for time-series results. The only usage-flavored content is the top_n cap, which is parameter documentation rather than routing guidance.

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