worstVendor

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does reveal the core metric ('highest transaction failure rate') and implies a read-only operation via 'Retrieve,' but it does not explain the time window, transaction scope, or how the failure rate is calculated.

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 efficient sentence that front-loads the action and resource, then adds a concise parenthetical definition. Every word earns its place with no redundancy or filler.

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 zero-parameter read-only tool with no output schema, the description is reasonably complete: it names the result and defines the criterion. It could add detail about the returned fields or result format, but the low complexity and absence of parameters reduce the burden.

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 has zero parameters, so the schema provides no semantic content. The description adds meaning by defining the result concept, which is the only parameter-related context needed for an empty input 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 uses a specific verb ('Retrieve') and resource ('the worst processing vendor'), and defines the key term precisely as 'the vendor with the highest transaction failure rate.' This is clear and distinguishes the tool from topVendor, though it does not explicitly name related siblings like vendorPerformance or vendorComparison.

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 guidance is provided about when to use this tool versus alternatives. With siblings like vendorPerformance, topVendor, and vendorComparison, the description does not state when worstVendor is the appropriate choice or what distinguishes it beyond its name.

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