pcb_get_schematic_page

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

No annotations exist, so the description carries the full burden. It does disclose the output contents and the optional pymupdf dependency for image rendering, but it does not state whether the operation is read-only, error behavior for invalid sessions/page numbers, or any side effects.

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 outputs, then optional rendering. Every sentence provides value and there is no redundancy.

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, the description does explain the main return values. However, it does not mention the prerequisite session_id or page number bounds, and the output format is only listed at a high level. For a simple getter, this is mostly complete but has minor gaps.

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% for all three parameters, each with meaningful descriptions. The tool description adds no parameter-specific details beyond the schema; the pymupdf dependency for render_image is already captured in the schema.

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 the tool gets extracted text and annotations for a specific schematic PDF page, and lists the specific outputs (page text, components, net labels). This distinguishes it from sibling tools like pcb_parse_schematic_pdf, which parses the whole schematic, and analysis tools.

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 no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites such as needing a session from pcb_parse_schematic_pdf or that for the full schematic one might use a different tool. Usage context is only implied by the schema parameter description.

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