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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no restating. The description adds which metrics the timeseries contains, but says nothing about granularity (daily/weekly), data freshness, gaps for new trackers, or whether the window is rolling — behavior an agent would benefit from knowing.

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?

A single front-loaded sentence with the metric list up front and no filler. It is efficient, though the telegraphic 'Timeseries of ...' phrasing could be tightened into a complete statement of what the call returns.

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?

This is a simple two-parameter read-only tool with an output schema, so return-value explanation is not required, and the schema covers parameter detail. The metric list tells the agent exactly what the response measures, leaving no material gap for correct invocation.

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 both parameters are fully documented in the schema, including the 1-365 bound and the default of 90 days plus where tracker_id originates. The description adds no meaning beyond 'for a citation tracker', so the baseline of 3 applies.

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 (timeseries of mention rate, citation rate, share of voice, average position) scoped to a single citation tracker, so an agent can tell it apart from configuration tools like get_citation_tracker or update_citation_tracker. It stops short of explicitly contrasting with siblings such as history or geo_monitor_history, which is why it is not a 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?

There is no when-to-use or when-not-to-use statement, and no alternative tool is named. The only implied guidance is that a tracker_id is needed, which the agent already infers from the parameter name and schema.

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