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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing the underlying methodology (pageviews plus news coverage versus a 30-day baseline), which explains why items appear. It does not state result ordering, refresh cadence, or how many categories may be combined.

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 sentence with the ranking signal front-loaded and the data sources in parentheses. It is a noun phrase rather than a full clause, but nothing is redundant or padded.

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 two-parameter read tool with no output schema, the description covers what the entity is and how ranking is computed, which is the core need. It leaves open what fields come back per person and whether results are ordered by spike magnitude, which an agent would want before presenting results.

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 50%: the category enum values are already documented in the schema, while limit is not. The phrase 'by category' in the description confirms category acts as a filter but adds no syntax or default-behavior detail beyond the schema. 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 resource (public figures) and the exact ranking signal (attention spike measured via Wikipedia pageviews and news coverage against a 30-day baseline). This is clearly distinguishable from topic- or story-oriented siblings. It stops short of explicitly contrasting itself with news_trending or news_trending_topics.

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?

Usage is only implied: an agent can infer this is the tool for 'who is spiking in attention right now', and the metric definition helps it judge fit. There is no explicit when-to-use, when-not-to-use, or named alternative among the trending siblings.

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