jlcpcb_tdp_calculate_price

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It discloses that no order is placed (read-only), states that API credentials are required, and identifies it as official. This covers key behavioral aspects, though it does not mention return format or error conditions.

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 concise sentences, front-loaded with the main purpose and immediately clarifying the non-order behavior. Every word adds value with no 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?

For a price calculation tool with one nested object parameter, the description covers the essential parameters, credentials, and side-effect freedom. It is sufficient for a task of this complexity, though a brief note on return value format would make it fully 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?

Schema coverage is 100% and the schema already lists the same parameter keys as the description. The description reiterates these keys but adds no deeper semantic meaning beyond what the schema provides, such as types, constraints, or relationships between 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 a specific verb ('calculate price') and resource ('3D-printing job'), and explicitly distinguishes itself by clarifying that it is a quote and no order is placed. This differentiates it from sibling tools like jlcpcb_tdp_create_order and jlcpcb_pcb_calculate_price.

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 clearly indicates the tool is for pricing a 3D-printing job and that it does not place an order, which implies when to use it before order creation. However, it does not explicitly name alternatives or state when not to use it, though the context is fairly clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.