Open a durable warranty claim on an accepted order or specific order line. This records the claim and notifies the supplier without asserting eligibility or approval.
| Name | Required | Description | Default |
|---|---|---|---|
| order_id | Yes | ||
| description | Yes | ||
| order_item_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
| order | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate non-read-only, open-world, non-idempotent behavior. The description adds valuable specifics: it 'records the claim and notifies the supplier' and explicitly states it does 'not assert eligibility or approval,' which goes 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 two sentences with the main action front-loaded and a concise behavioral nuance following. 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?
The description covers the purpose, target, and side effects effectively. With an output schema present, it does not need to explain return values. It omits explicit mention of required parameters, but that detail is already in the schema, making the description adequately complete.
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?
With 0% schema description coverage, the description partially compensates by implying order_id refers to an accepted order and order_item_id to a specific line. However, it provides no semantic detail for the required 'description' parameter, leaving its purpose to be inferred.
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 the specific verb 'open' with the resource 'durable warranty claim' and clearly identifies the target as 'an accepted order or specific order line.' This distinguishes it from sibling tools like update_supplier_warranty_claim and request_order_return.
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?
It provides clear context for when to use the tool: on an accepted order or specific order line, and clarifies it does not assert eligibility or approval. However, it does not explicitly name alternative tools or state when not to use this tool, so it stops short of a full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool targets a distinct resource, role, or action. For example, list_orders versus list_supplier_orders clearly separates buyer and supplier views, and update_supplier_order versus update_supplier_order_issue versus update_supplier_order_return handle different concerns despite similar names. Rich descriptions eliminate ambiguity.
All tool names consistently use snake_case with a verb_noun pattern (e.g., create_project, list_orders, update_supplier_capabilities, search_products). The style is uniform across reads, writes, lists, and searches, making the API predictable.
With 55 tools, the server far exceeds the typical well-scoped range of 3-15. Even for a broad supply chain platform, 50+ tools hits the rubric's 'extreme mismatch' threshold. The domain is comprehensive, but the sheer number overwhelms and likely complicates agent tool selection.
The tool surface covers the full lifecycle from project creation, BOM management, sourcing, quoting, planning, checkout handoff, orders, returns, issues, warranties, catalog updates, supplier profiles, and validation. It handles buyer and supplier sides with appropriate state transitions, and includes meta tools for connection and schema guidance. No obvious critical gaps exist.