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

No annotations are provided, so the description must disclose behavioral traits. It only describes the data returned (scores, claims, counts) but does not state whether the operation is read-only, what happens on a non-existent vendor (error vs. null), or any side effects. For a get operation, read-only is implied but not confirmed, and error behavior is unaddressed.

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 is a single, dense sentence that front-loads the purpose ('One research peptide vendor's public trust record') and enumerates the key data points without redundancy. Every clause earns its place, making it efficient and scannable.

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?

Given the tool's simplicity (one parameter, no output schema), the description adequately covers the return content by listing the major fields. The only gap is lack of detail on failure behavior (e.g., missing vendor), but for a straightforward get this is a minor omission. The description is largely complete for an agent to call it correctly.

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 schema already fully documents the single parameter 'vendor' with an example ("Certified Peptides"). The description adds no additional meaning or formatting guidance beyond what the schema provides, so a baseline score of 3 is appropriate given high schema 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 the specific verb 'get' and resource 'vendor record' with a detailed list of contained fields (Peptul Score, COA verification, review counts, issues, shipping, operating status). This clearly differentiates it from siblings like search_vendors (which searches) and get_compound_prices (which is price-focused), making selection unambiguous.

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?

The description implies usage: use this tool when you need a specific vendor's public trust record. It does not explicitly mention when not to use it or name alternatives, but the context of sibling tools and the description's specificity make the intended use reasonably clear. Lacks explicit exclusions or comparison to alternatives.

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