printing.orders.getPoll the payment and manufacturing status associated with a credential-owned quote.
| Name | Required | Description | Default |
|---|---|---|---|
| quoteId | Yes | AIURION quote UUID returned by printing.quotes.create. | |
| accessToken | No | Guest token returned by printing.sessions.start. Optional when Authorization already carries a permanent key or guest token. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds context by specifying 'payment and manufacturing status' and 'credential-owned', reinforcing the read-only, auth-oriented nature of the operation. However, it does not mention rate limits or additional side effects, but with annotations 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?
The description is a single, front-loaded sentence that states the action, object, and context without waste. Every word adds value, making it highly concise and well-structured.
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 simple two-parameter tool with output schema, annotations covering safety, and full parameter schema descriptions, the description is complete enough. It conveys the core purpose and relies on structured data for details, which is sufficient.
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 100%; both parameters (quoteId and accessToken) are fully explained with provenance from other print tools. The description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.
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 'Poll' and clearly identifies the resource ('payment and manufacturing status') and the scope ('credential-owned quote'). This distinguishes it from siblings like printing.quotes.get, making the tool's purpose unambiguous.
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 verb 'Poll' and the phrase 'associated with a credential-owned quote' imply this tool is used after a quote is created to check status. Context is clear, but it does not explicitly state when to avoid using it or name alternatives, 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.
Each tool targets a distinct resource/action: capabilities, checkout, orders, quotes (create/get/update), and sessions. There is no overlap in purpose, so an agent can unambiguously select the correct tool.
All tool names follow a consistent dotted pattern: printing.<resource>.<action>. Verbs are uniform (get, create, update, start) and snake_case is used throughout, making the API predictable.
Seven tools is well-scoped for a 3D printing service, covering the main workflow (capability discovery, session creation, quote management, checkout, and order tracking) without redundancy or bloat.
The surface covers the core lifecycle: capabilities, session, quote CRUD (create/get/update), checkout, and order status. A minor gap is lack of explicit delete/cancel operations, but these can be worked around via update or are not essential for the stated flow.