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

Beyond the read-only and idempotent annotations, the description discloses important behavior: the result is not-collected with null statistics, documentation is not reviewed, vendor integrations are untested, only retained current observations are available, and historical batch queries are rejected. These are substantive behavioral limitations that an agent would not know from annotations alone.

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 front-loads the key result behavior in the first two sentences, but later sentences are dense and somewhat cryptic. Phrases like 'matched/guide entries are explicit local references' add ambiguity rather than cleanly supporting tool selection.

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?

There is no output schema, so the description must explain return behavior; it does so by stating that the result is not-collected with null statistics. It also covers key limitations and safety context, though it remains somewhat unclear about how interfaceId and capability interact with the candidate-set behavior.

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 80%, so most parameter meaning is already documented in the input schema. The description adds little about individual parameters such as softwareId, interfaceId, capability, language, or locale, beyond implying that historical batch queries are unavailable.

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 states that this candidate review-summary tool returns not-collected with null statistics because the selected candidate set has no human review evidence. It also distinguishes the result from a zero rating or a formal catalog review summary. The purpose is clear despite awkward phrasing.

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 the tool is only for the selected candidate set and that historical batch queries are not accepted, which helps constrain usage. However, it does not explicitly point to the sibling get_review_summary or clearly state when an agent should choose this tool instead of alternatives.

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