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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description's one genuine addition is the return payload composition and the 20-record review cap, which matters because there is no output schema; it says nothing about permissions, missing-capability behavior, or environment scoping.

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 no filler. It is arguably too terse for a tool with three required lookup keys, but nothing in it is wasted.

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 no output schema, the description does just enough by listing the returned components and the review limit. It leaves the capability-slug source and the company/environment scoping of results unexplained, which a caller assembling the three required identifiers would want.

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 67%: `company` and `environment` are documented inline, and `environment` has an enum, while `capability` is described only by its regex pattern. The description adds no meaning beyond the schema, so the baseline 3 applies for middling coverage.

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 concrete verb ('Read') and resource ('one capability') and enumerates the payload (test, evidence, latest 20 review records), so an agent knows exactly what it gets back. It never names or contrasts with sibling `summer_capability_checks_list` / `_test` / `_save`, so the singular-vs-list distinction is only implied.

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 guidance on when to use this versus `summer_capability_checks_list` (enumerate) or `summer_capability_checks_report`, nor any stated prerequisites such as knowing the capability slug. The 'one' qualifier hints at single-record retrieval but no alternative is named.

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