Test coverage by product

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering safety and completeness. The description adds that it provides an overall rollup and untested tickets per product, but does not disclose further behavioral traits like data recency or permission requirements typical for aggregation tools.

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 two sentences long, front-loaded with the main action and output. It efficiently conveys the purpose and result. However, it could be slightly more structured by explicitly linking the parameter to the products.

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 no output schema, the description compensates partially by stating it returns an overall rollup and untested tickets per product. However, it lacks details on the output format (e.g., counts, lists, or maps) and does not explain the parameter 'project' in relation to products, leaving some ambiguity for an AI agent.

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 0% (no parameter descriptions in the schema). The description mentions 'per product' but the only parameter is 'project', without clarifying the relationship between project and product. This ambiguity can lead to misuse. The description should explain what the project parameter means in context.

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 the tool rolls up test coverage per product, comparing tickets with and without recorded test runs. It specifies the output includes an overall rollup and untested tickets per product, which distinctly sets it apart from sibling tools like 'get_test_runs' or 'test_runs_by_suite'.

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 explicit guidance on when to use this tool versus alternatives. The description implies it's for viewing testing gaps on a board, but does not mention conditions, prerequisites, or scenarios where other tools might be more appropriate. Given the large number of sibling tools, this is a gap.

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