verify_pcb_revision

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so safety is partly covered. The description adds useful context that the checks are 'real' and produce 'revision-bound evidence', which is consistent with the non-read-only hint, but it does not say what evidence is produced, where it is stored, or whether it can fail or be costly.

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?

A single front-loaded sentence with no filler; the action, the check categories, and the evidence qualifier all earn their place.

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?

There is no output schema and the description does not explain what the returned evidence looks like or how to act on failures, which matters for a verification tool. Combined with zero parameter documentation and no annotation coverage of the actual side effects, the definition is too thin for correct invocation.

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% and the description never mentions the two required parameters (project, revision). For a tool that is bound to a specific revision, the agent gets no clarification of what form an identifier takes or how 'revision' relates to the revision list returned by list_pcb_revisions.

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?

Names a specific action (run ERC/DRC, connectivity and geometric checks) against a specific resource (a PCB revision), and 'revision-bound evidence' signals the output nature. It is clearly distinct from a generic 'inspect' tool, though it never names or contrasts with the closest sibling inspect_pcb_revision.

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?

There is no when-to-use guidance, no prerequisites, and no indication of how this differs from inspect_pcb_revision or diagnose_pcb_repair. The word 'real' hints that some other path produces simulated checks, but the agent is left to infer when that tradeoff matters.

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