pcb_parse_schematic_pdf

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

With no annotations provided, the description carries the burden of behavioral disclosure. It usefully discloses the text-layer extraction dependency, pymupdf requirement, and the session-attaching side effect. However, it does not mention what happens when the text layer is absent, error conditions, or the structure of the returned data.

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 sentences, front-loaded with the primary action, then a concise dependency note, then the optional behavior. No filler or redundancy; every sentence contributes useful information.

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 the simple 2-parameter schema and no output schema, the description covers the core purpose, an important dependency/limitation (text-layer extraction, pymupdf), and the optional session attachment behavior. It does not delve into return format or failure modes, but the main usage context is sufficiently clear for an agent to select and invoke the 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?

Schema description coverage is 100%, so the baseline is 3. The description adds minimal meaning beyond the schema: it reiterates file_path as the PDF path and session_id as the session to attach to, and adds the kind of data extracted (component references, net labels, page data) but no new parameter-specific details.

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 'Parse' and clearly identifies the resource ('PDF schematic') and the extraction targets ('component references, net labels, and page data'). It also distinguishes itself from sibling tools like pcb_parse_schematic by explicitly focusing on PDF input and text-layer extraction.

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 provides clear context for when to use this tool: for parsing PDF schematics with a text layer, and notes the dependency on pymupdf. It also explains the optional session_id behavior, though it does not explicitly mention alternatives or exclusions relative to sibling tools.

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