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

Annotations already declare readOnly, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: a fixed 30-day window, and two explicit disclaimers (not a score, not a truth judgement) that prevent an agent from over-reading the output.

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 first sentence front-loads the core comparison, and the disclaimers land before the rhetorical question. The opening clause ('how much of the claim activity Horizon holds provenance data for is self-reported...') is syntactically tangled and could be shorter, but no sentence is redundant.

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?

An output schema exists, so return values need no prose explanation, and annotations plus the 30-day scope cover most behavioral questions. What remains unaddressed is edge-case handling — what happens for an unknown or ambiguous entity name — which matters for a single-required-string lookup.

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% and the schema already supplies a concrete example, so the baseline is 3. The description adds meaning on top by stating the entity may be a company, a model, or a person, which broadens and disambiguates the parameter's accepted domain beyond the single example.

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 verb-and-resource combination (provenance breakdown for a single entity) and defines the two quantities being compared: self-reported versus independently evaluated claim activity. This is clearly distinct from the sibling signal/search tools, which report topical or regional activity rather than an attribution split.

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?

It supplies a concrete use case ('is the buzz around X coming from X?') and explicitly bounds the output as descriptive counts over the last 30 days, not a score or truth judgement. It never names an alternative tool or states when not to use it, so it falls short of a full when/when-not specification.

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