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

No annotations are present, so the description carries the full burden. It does disclose a meaningful behavioral trait: LCSC numbers are unverified and left blank, which is important for users. However, it does not mention side effects, errors, or any other behavioral constraints beyond that.

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, focused sentence that efficiently conveys the output format and a critical caveat. Every word earns its place, with no redundancy or unnecessary detail.

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 is simple, but the description is incomplete: it never explains the 'prompt' parameter, provides no usage context, and lacks an output schema. The caveat about LCSC numbers is useful, but the missing parameter semantics and usage guidance prevent the description from being complete for an agent.

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 only parameter, 'prompt', has no schema description and the schema coverage is 0%. The description does not explain what the prompt should contain, how it relates to the BOM CSV, or any format/constraints. The agent cannot correctly determine how to populate this parameter.

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 that the tool returns a BOM CSV in JLCPCB format with specific columns (Comment, Designator, Footprint, LCSC). This is a specific verb+resource+scope and distinguishes it from sibling tools like get_netlist and get_placement.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention prerequisites, typical scenarios, or when another tool (e.g., get_netlist) would be more appropriate. The JLCPCB-specific format is the only implicit hint.

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