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

readOnlyHint=true already tells the agent this is a safe read, so the description's main added value is the bucketing-by-interval behavior and the underlying REST endpoint. It says nothing about how pagination interacts with bucketing or what happens when a branch/date range yields no data, leaving real behavioral gaps. Some value added, but not rich.

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?

Two compact sentences with the purpose front-loaded and the endpoint reference appended as supporting detail. Every clause earns its place; there is no filler.

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 9-parameter read tool with no output schema, the definition is adequate but thin: it does not describe the shape of the returned time series or how paging and interval interact, which an agent calling this correctly would benefit from knowing. Annotations cover safety and the schema covers parameters, so it is minimally viable rather than 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 100% (interval, service, branch, start/end date, paging are all documented in the schema), so the baseline is 3. The phrase 'bucketed by interval' adds a little semantic weight to the interval parameter, but nothing beyond what the schema already conveys.

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 and resource: 'Coverage measurements over time for a repository, bucketed by interval.' This is clear and actionable, and the REST endpoint mapping reinforces the resource. However, it never distinguishes itself from the sibling codecov_get_flag_coverage_trend, so an agent must infer that this one is repo-scoped rather than flag-scoped.

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?

No when-to-use guidance at all: nothing says when a trend query is preferable to codecov_get_coverage_totals or the flag-level trend sibling. The name implies usage, but there are no stated conditions, prerequisites, or exclusions.

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