inspect_pcb_inventory

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

Annotations already establish the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description adds genuine context beyond them: results are paginated and must be drained, and incomplete data ("missing metadata and unverified connectivity") is surfaced explicitly rather than silently dropped. It does not cover ordering or what a partial page means.

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 tight sentences with the primary capability front-loaded and the operational/pagination note second. Nothing is padded, though the second sentence compresses three distinct ideas into one clause.

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?

With no output schema and 0% parameter coverage, the description needs to do more. It never explains the section-driven response shape, the meaning of the required project/revision pair, or how search interacts with paging, leaving an agent under-informed for a six-parameter inspection 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 0% across six parameters, so the description carries the full burden and largely fails. The data domains loosely hint at the section enum values, and "page until total is exhausted" gestures at limit/offset, but search, project, and revision semantics are never explained.

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?

States a specific verb ("Read") and enumerates the resource domains (component, pin, network, copper data) bound to a revision. This is clear on its own, but it never distinguishes itself from the sibling inspect_pcb_revision or list_pcb_revisions, so an agent has to guess which read tool fits.

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?

"Page until total is exhausted" gives real operational guidance on how to consume the result, but there is no statement of when to use this over inspect_pcb_revision or list_pcb_revisions, and no prerequisites. Usage is implied by the resource domains rather than stated.

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