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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral context: the underlying data source (Wikimedia pageview data, CC0) and the range/latency constraint of 7 to 90 days. It doesn't mention caching, rate limits or data latency, which keeps it from a 5.

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?

One dense, front-loaded sentence that leads with what the tool returns before the input guidance. Efficient with no filler, though the long parenthetical enumerating entity types and outputs makes it slightly heavy to parse.

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?

With an output schema covering return values and annotations covering the safety profile, the description only needs to add the entity scope, the title-exactness caveat and the data provenance - all present. An agent has everything required to call it 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?

Schema coverage is 100%, so title/lang/days are already documented in the schema, making 3 the baseline. The description only reinforces the exact-title requirement and the 7-90 range with an example ("Bitcoin") but adds no format or fallback semantics beyond the schema.

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?

States a specific verb+resource: daily Wikipedia pageviews for one article, scoped to a titled entity and 7-90 days, returning baseline, latest-vs-baseline, spike days and 7-day trend. This distinguishes it clearly from aggregate siblings like list_trending_topics, list_attention_spikes and list_attention_markets.

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?

Gives a concrete usage instruction ("Use the exact article title, e.g. Bitcoin") which is the main failure mode for this tool. It doesn't name alternatives or when-not conditions (e.g., use list_attention_spikes for pro-active discovery), so it stops short of a 5.

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