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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description adds real value by disclosing the shape of the response — sources with read dates and a watch.state field with offer_url/manage_url — plus the polling implication of 'as they arrive'. It does not mention error behavior for an unknown or foreign request ID.

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 dense sentence that front-loads the verb and resource, then layers in return content and required inputs. No filler, though the watch.state parenthetical is slightly cryptic without a framing clause.

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 only two required parameters, no output schema, and annotations covering the safety profile, the description supplies enough: what is returned (sources, read dates, watch status), the polling expectation, and the credentials needed. Only the failure mode for an invalid request ID is unaddressed.

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 0%, so both parameters lack structured documentation, but the description compensates partially by explaining that the email must be the one that submitted the list (an ownership constraint) and that the ID identifies the check request. It does not state the uuid/email format expectations or whether the email is used for authorization.

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 and resource ('Read your vendor check results') and names the returned content (sources, read dates, watch state), which lets an agent separate it from the sibling vendor_check_request that initiates checks. It stops short of explicitly naming the sibling it is not.

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?

'as they arrive' implies a poll-until-complete usage pattern, and 'Use the request ID and the email that submitted the list' tells the agent what identifying context it needs. There is no explicit statement of when to prefer this over vendor_check_request or what to do if results are incomplete.

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