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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact: the review records are truncated to the latest 20, which tells the agent the return is bounded rather than paginated. It says nothing about required authorization or scoping beyond what the schema implies.

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 or redundancy - the payload contents come after the verb+resource, which is the right order. It is penalized only because it duplicates the title word-for-word rather than using its one sentence to add information.

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 must describe the return, and it does name the four returned elements, which is adequate for a read-only get. However, it omits what happens when the capability does not exist, whether the 20 review records are paginable, and how company/environment scope the lookup - gaps that matter for a tool whose whole purpose is fetching a composite record.

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 67%: company and environment carry descriptions, but the required 'capability' identifier (with its ^[a-z][a-z0-9_]{1,79}$ pattern) is undocumented. The description adds no parameter meaning at all, not even clarifying that the capability slug is the same key used by the sibling list/report tools, so it fails to compensate for the coverage gap.

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 (Read) and a specific resource (one capability) and even enumerates the payload it returns: the concrete test, evidence, and latest 20 review records. It is clear what the tool does, but it does not distinguish itself from siblings like summer_capability_checks_list, _report, _save or _test, and the sentence is a verbatim restatement of the title.

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 when-to-use guidance, no prerequisites, and no routing to alternatives, even though the sibling set contains four other capability-check tools (list, report, save, test) that an agent must choose between. The agent can infer it is the singular-read counterpart to the list tool, but the description never says so.

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