gate_production_readiness

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the description's value is in disclosing the pipeline breadth, the exact bundle contents (copper, mask, silk, stencil, drill, BOM, CPL) and the validation depth including solder-mask dam width. It also states the return contract (single verdict plus blocking defects) despite no output schema. It omits whether exported artifacts persist on disk and rough runtime expectations for such a heavy pipeline.

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?

Two sentences, front-loaded with the one-call gate framing and ending with the consumer-facing outcome; every clause carries information. The comma-heavy enumeration of bundle layers is dense but earns its place by defining the '9-layer' claim.

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 complex multi-stage tool with no output schema, the description does well on outcome and validation scope, but three of four parameters are undocumented here, and side effects of 'export' are left ambiguous against a readOnlyHint=true annotation. It is adequate, but a caller could still be surprised by cost or artifacts.

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 only 25% (only 'prompt' is documented), so the description is obliged to compensate for job_name, board_width_mm and board_height_mm — and it says nothing about any of them. An agent cannot learn from the text whether the board dimensions constrain synthesis or what job_name scopes.

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 composite verb chain (synthesize → place → autoroute → export → validate) over a specific resource (the 9-layer fab bundle) and states the deliverable (a production_ready verdict). It is clearly separable from siblings like validate_manufacturing_package or export_gerber_bundle because it declares itself a one-call aggregate of those steps.

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 frames the usage context explicitly — a CI job or contract manufacturer making a go/no-go decision — and implicitly positions itself against calling the individual reporting tools with 'without reading five separate reports'. It does not name specific sibling tools or state when not to use it (e.g., when iterating on a design), so it stops short of the top score.

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