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

The readOnlyHint annotation already tells the agent this is a safe read, so the bar is lower. The description adds useful context via the underlying REST path and the filterable facets, but says nothing about pagination behavior, default result counts, or ordering, which matter for a list endpoint with page/pageSize.

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 tight sentences with the purpose front-loaded and the REST endpoint appended as a compact reference. No filler, no redundancy.

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?

With a readOnly annotation and no output schema, the description covers purpose and filters adequately; return values need not be explained. It is only slightly short of complete because it omits mention of pagination, which is relevant given the page and pageSize parameters.

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%, so the schema already documents every parameter including enums and units. The description echoes the filter set (branch, commit, outcome, duration) but adds no syntax or format detail beyond what the schema provides, 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?

States a specific verb ('List') and resource ('repository's test-analytics results'), with the scope and optional filter axes spelled out, plus the exact REST endpoint. This distinguishes it clearly from sibling list tools such as codecov_list_commits and codecov_list_commit_uploads.

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 implies when the tool is useful by naming the filterable dimensions (branch, commit, outcome, duration), but it never states when to prefer it over alternatives or any prerequisites (e.g. needing a report to exist for the commit). Usage is implied rather than prescribed.

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