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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine value by disclosing what comes back — vendor, pricing-checked date, and pricing page URLs — which is important given there is no output schema. It does not say whether the list is static or refreshed, hence not 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?

A single sentence with no filler, and the most decision-relevant information (which vendors, how fresh the pricing is, where the source pages are) is packed in without preamble.

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 and no parameters, the description carries the return-value burden and does so adequately by enumerating the three fields returned. The one unresolved ambiguity is the referent of 'the estimate' — an agent cannot tell whether this requires a prior estimate_cost call or reflects a fixed vendor set.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. Nothing in the text conflicts with the empty schema.

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 names the resource (vendors) and the payload it returns: pricing-check date and official pricing page URLs. That is enough for an agent to distinguish it from the only sibling, estimate_cost, which computes numbers rather than listing sources. It loses a point because it is phrased as a noun fragment ('Vendors covered by the estimate') rather than an explicit verb+resource statement.

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 statement of when to call this versus estimate_cost, no prerequisite (e.g. must a cost estimate be run first for 'the estimate' to exist), and no exclusions. The agent must infer the usage purely from the returned-content phrasing.

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