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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the data source (Wikimedia pageview data, CC0) and the output elements, but it doesn't state whether the operation is read-only (implied but not explicit), whether there are rate limits, authentication requirements, or any side effects. For a data retrieval tool without annotations, more could be said to clarify behavior.

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?

The description is a single sentence that is front-loaded with the core purpose and output details, followed by a usage tip and data source. It is efficient with no wasted words, though the parenthetical use case list could be seen as slightly verbose.

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?

Given three parameters, no output schema, and no annotations, the description covers the purpose and output elements but misses some contextual details like the behavior of the lang parameter, potential limitations (e.g., data freshness), and explicit differences from sibling tools. It is adequate but not fully complete.

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 67%, with parameters days and title having descriptions ('7 to 90' and 'Exact Wikipedia article title'), while lang has none. The description adds some semantic meaning by stating 'Use the exact article title, e.g. Bitcoin,' which reinforces the title requirement, but it doesn't explain the lang parameter or provide additional format details for days beyond the schema. Baseline 3 is appropriate given moderate coverage.

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 clearly states a specific verb and resource: 'Attention history for any topic: daily Wikipedia pageviews of one article...' with detail on what is returned (baseline, latest day vs. baseline, spike days, 7-day trend). It distinguishes itself from sibling tools like attention_spikes and attention_trending by focusing on a single article's history over 7-90 days. However, it doesn't explicitly differentiate from those siblings, so it's not a perfect 5.

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 implicitly conveys when to use by specifying 'one article' and the range, but it does not provide explicit guidance on when to choose this tool over alternatives like attention_spikes or attention_trending. No exclusions or prerequisites are mentioned. This is minimal viable guidance.

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