compare_component_offers

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

Annotations already declare the tool read-only, open-world, and idempotent. The description adds contextual behavior beyond these: it emphasizes 'strict' matching, indicating only exact manufacturer-plus-MPN matches are considered, and that quantities affect the comparison. This gives insight into the matching logic and scope, which is valuable beyond the annotations.

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 concise sentence that front-loads the action and resource, with no filler or redundant wording. Every word contributes meaning: 'strict', 'manufacturer-plus-MPN', 'requested quantities', and 'across DigiKey and Mouser' all add essential clarity.

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 has one nested parameter and no output schema, the description conveys the core purpose and scope sufficiently. It states the matching criteria and the vendors involved. It could mention the response format or what happens with missing matches, but the annotations cover safety and idempotency, and the purpose is clear enough for an agent to select and invoke the tool.

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 description coverage is 0%, but the description indirectly references the key required fields: 'manufacturer-plus-MPN' corresponds to manufacturer and manufacturer_part_number, and 'requested quantities' maps to quantity. This adds meaning to the schema. However, it does not explain the nested structure of the 'request' object (e.g., that items is an array), so compensation is partial.

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 clearly states the tool's function: comparing strict manufacturer-plus-MPN matches at requested quantities across DigiKey and Mouser. It uses a specific verb ('Compare') and identifies the exact resource (manufacturer-plus-MPN matches) and scope (DigiKey and Mouser), effectively distinguishing it from siblings like search_products or get_product_pricing.

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 provides clear context for when to use the tool: when you need to compare exact manufacturer and part number matches across two specific distributors at given quantities. However, it does not explicitly state when not to use it or mention alternative tools for similar tasks, so it stops short of full guidance.

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