Get quotes for an RFQ item (L1/L2/L3)

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

No annotations provided, so description carries full burden. It describes the return fields (price, lead time, remarks, response_id, rank_label) and notes that L1 is price-only. No side effects or rate limits mentioned, but for a read operation this is sufficient.

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?

Two sentences with no wasted words. The first sentence explains the core operation, the second adds an important caveat about L1 ranking. Front-loaded with key info.

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 tool with 1 parameter and no output schema, the description is fairly complete. It explains the output fields and ranking logic. Could mention default sorting or pagination, but not necessary.

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 coverage is 100% (1 parameter fully described). The description adds value by specifying where to obtain the rfq_item_id (from list_rfqs or create_rfq) and the exclusiveMinimum constraint, going beyond the 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 clearly states the verb 'Pull' and the resource 'all supplier quotes for one RFQ line item', distinguishing it from siblings like create_rfq or place_order. It also explains the unique L1/L2/L3 ranking feature.

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?

Provides guidance on interpreting L1 ranking and reminds to weigh other factors before awarding. However, it doesn't explicitly state when to use this tool vs alternatives like list_rfqs or place_order, though it's implied.

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