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

With no annotations, the description carries the full burden and does well: it enumerates returned fields, defines slowTestCount (success mean > 30s), and warns that the sum of means is aggregate CPU-time rather than CI wall-clock under parallelism. It omits auth/permission and rate-limit context, keeping it just short of a 5.

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?

Front-loaded with the core action and packed with useful specifics; each sentence (returns list, CPU-vs-wall-clock caveat, budget comparison) earns its place. Dense but not padded.

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?

Since no output schema exists, the description appropriately enumerates the returned fields, and the caveat is valuable. But with 10 parameters at 0% schema coverage and no annotation coverage, the definition is incomplete on the input side for a tool of this complexity.

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% across 10 parameters, including a nested scope and dimensionFilters object, and the description explains none of them individually. Pointing to 'same filters as get-execution-history' is only partial compensation for such a large undocumented surface.

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+resource (aggregate suite timing stats) and distinguishes itself from siblings by noting it derives from list_execution_history testStats and shares filters with get-execution-history. An agent can tell this is the aggregated-stats variant rather than a raw history fetch.

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 implies usage by stating 'this tool only returns stats' and referencing get-execution-history for filters, and advises comparing sumSuccessMeanSecs against a suite budget. However it never explicitly states when to pick this over get-execution-history or what the filters actually are, leaving routing partly to inference.

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