vendorPerformance

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

No annotations are present, so the description must carry the behavioral disclosure burden. 'Retrieve' implies read-only, but it does not disclose output format, time window, or behavior for invalid/unknown vendor IDs.

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 that is front-loaded with the action and immediately lists the deliverables. No filler or redundant content.

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?

For a simple one-parameter read the description is mostly sufficient, but the absence of any time-range or unit context and no usage guidance leaves minor ambiguity about what period the vendor performance covers.

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 describes vendorId with examples and has 100% coverage. The description adds no parameter-level semantics beyond the list of returned metrics, matching the baseline for 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 a precise verb ('Retrieve'), names the resource (vendor performance), and enumerates the exact metrics returned. The qualifier 'for a specific vendor' sets it apart from aggregate/comparison siblings, though it does not name them explicitly.

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?

No when-to-use or alternative routing guidance is provided. The description only says what the tool does, not when to prefer it over vendorComparison, topVendor, or getDashboardMetrics.

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