List what can be printed: SKUs (storybook books, sticker-a3 wall charts, greeting-card-a5 folded cards), formats, supported trim sizes, page-count limits, prices (INR, shipping included), and shipping coverage (India only). Call this first to quote a price or check whether a PDF will be accepted.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of disclosing behavior. It states the output contents (SKUs, formats, sizes, page-count limits, prices with INR and shipping included, shipping coverage India only) and its purpose (first step for pricing/PDF acceptance). This adds meaningful context about what the tool returns and its role, though it doesn't explicitly state it's read-only or non-destructive.
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, well-front-loaded sentence. It opens with the core action 'List what can be printed' and then efficiently enumerates all relevant catalog attributes without unnecessary fluff. Every clause adds value.
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?
Given no output schema, the description adequately explains what the tool returns by listing the types of data (SKUs, formats, sizes, page counts, prices, shipping coverage). It also puts the tool in context with 'Call this first', making it complete for a low-complexity catalog listing tool.
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, so the description doesn't need to explain parameter usage. The description still adds value by outlining the catalog contents, which inherently communicates what information the tool provides. Baseline for 0 params is 4.
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: 'List what can be printed' followed by a detailed enumeration of catalog contents (SKUs, formats, sizes, prices, shipping). It distinguishes itself from sibling tools like create_order, validate_pdf, and get_order by focusing on catalog data rather than order/validation operations.
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 explicitly instructs when to use the tool: 'Call this first to quote a price or check whether a PDF will be accepted.' This provides clear context for use, though it doesn't explicitly mention alternatives or when not to use it. Given the simple nature of the tool, this is strong guidance.
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 has a clearly distinct purpose: upload, validate, create order, get order, cancel order, list catalog, and enterprise application. There is no overlap between any two tools, making misselection highly unlikely.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_upload, cancel_order, get_catalog). The verbs are descriptive and the resources are clear, creating a predictable and uniform naming convention.
With 7 tools, the server is well-scoped for its purpose. It covers the complete print-order workflow without redundancy or excessive granularity, making the tool set easy to navigate.
The tool set covers the entire lifecycle from catalog browsing and upload validation through order creation, status tracking, and cancellation, plus enterprise account provisioning. There are no obvious missing operations that would hinder an agent in completing standard tasks.