printing.capabilities.getRead AIURION's supported 3D model formats, limits, materials, production options, and purchasing flow.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| 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, so the safety profile is known. The description adds context about the specific content returned (formats, limits, materials, production options, purchasing flow), which clarifies what the read operation exposes. It does not contradict 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 sentence that fronts the verb 'Read' and enumerates the key content areas in a compact list. Every phrase adds informational value without redundancy.
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 has no parameters and an output schema is present, so return values need no explanation. The description fully covers the scope of the tool for a read-only capabilities getter, making it complete given the simplicity.
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 input schema is empty with 100% schema coverage. Per the baseline for no-parameter tools, the description does not need to elaborate; it correctly avoids mentioning nonexistent parameters.
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 'Read' and identifies the exact resource: 'AIURION's supported 3D model formats, limits, materials, production options, and purchasing flow.' This clearly distinguishes it from sibling tools like printing.checkout.create or printing.quotes.get, which handle transactions rather than capability discovery.
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 does not explicitly state when to use this tool versus alternatives. The name 'capabilities.get' and read-only annotation imply it is a preliminary discovery tool, but no direct guidance or alternatives are mentioned, so usage context remains implied.
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.