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

No annotations exist, so the description carries the full burden. It usefully discloses the routing guarantees ('0 opens, 0 DRC') and that the call returns Stripe/Coinbase Pay (x402)/USDT-USDC payment instructions, but it never says whether invoking it creates an order, incurs cost, or runs asynchronously (a get_job_status sibling implies jobs) – notable given a 'requested_sku' default plus a 'customer_email' parameter.

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 alias claim and the returned artifacts are front-loaded, then the two modes are laid out in a compact parallel structure with no filler sentences. There is some duplication between the mode text and the schema parameter descriptions, but nothing wasteful enough to obscure the call path.

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 7-parameter tool with no output schema, an enum-typed SKU, and a stated payment side effect, the definition explains inputs adequately but omits what happens after submission – job lifecycle, whether payment instructions are informational or actionable, and which SKU to choose. An agent could call it successfully in Mode A but would be guessing on the ordering parameters.

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 57%, and the description compensates well for the file-input parameters, explaining sample IDs, accepted extensions, and the .PcbDoc/.zip base64 path. However, 'requested_sku' (a 7-value enum including 'turnkey_full') and 'customer_email' are entirely unaddressed in both the description and the schema, leaving the commercially important parameters unexplained.

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 names a specific verb and resource ('synthesize and route a PCB through Calligraphy EDA') and states the two accepted input paths, so the agent knows what it does. It is weakened by framing itself as an 'Alias for calligraphy_compile_board' without explaining why an agent should pick this entry point over the named sibling.

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?

Mode A and Mode B are spelled out with the exact parameters that select each ('sample_id' for the demo, 'pcb_text'+'filename' or 'upload_b64' for the user's own board), and it tells the caller to read local files first for remote HTTP. The gap is that it never says when to use this versus calligraphy_compile_board, which is the obvious alternative given the alias framing.

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