Read attributed live fabrication capabilities from the connected AFN provider. This is discovery only and neither uploads a design nor requests a quote.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| provider | Yes | ||
| source_url | Yes | ||
| attribution | Yes | ||
| observed_at | Yes | ||
| capabilities | Yes | ||
| commercial_boundary | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral nuance by emphasizing the discovery-only nature and stating what actions it does not perform, which goes beyond the annotations and provides valuable context.
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 consists of two concise sentences, with the first sentence clearly stating the purpose and the second adding an important boundary. Every word earns its place, and the information is front-loaded.
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 tool is simple (no parameters) and has an output schema, so the description does not need to explain return values. The description fully covers the tool's purpose and non-actions, and the annotations cover safety traits, making the description complete for effective use.
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, and the schema description coverage is 100%. Per the rubric, a baseline of 4 is appropriate when there are no parameters, as the description does not need to compensate for any parameter documentation gaps.
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 with a specific verb ('Read') and resource ('attributed live fabrication capabilities from the connected AFN provider'). It also distinguishes this tool from action-oriented siblings by noting it is 'discovery only' and does not upload designs or request quotes.
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 this tool (when you need to read capabilities without performing other actions) and explicitly states exclusions ('neither uploads a design nor requests a quote'). However, it does not explicitly name alternative tools, so it falls short of a 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.