pcb_compare_simulation

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only says 'validate accuracy' without explaining what the tool returns (e.g., pass/fail, percentage error), how tolerance_percent factors into the comparison, or what happens when values differ. This leaves significant ambiguity for an agent.

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, concise sentence that front-loads the primary action and purpose. Every word earns its place, with no redundancy or filler. It is highly efficient and easy to parse.

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 relatively simple and the schema documents all parameters, but there is no output schema and the description does not explain what the tool returns or how 'validate accuracy' manifests. Given the absence of annotations and output schema, the description should offer more detail on the expected result, making it partially incomplete.

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 input schema has 100% description coverage for all parameters, so the baseline is 3. The description itself adds little beyond the schema: it mentions 'analytical calculation' and 'simulation result' which map to analytical_value and simulated_value, but does not deepen understanding of unit or tolerance_percent beyond what the schema already provides.

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's function: 'Compare analytical calculation vs simulation result to validate accuracy.' It uses a specific verb ('compare') and identifies the two resources being compared, distinguishing it from sibling calculation tools like pcb_calc_microstrip_impedance and simulation tools like pcb_generate_em_simulation.

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 implies the tool should be used when both an analytical value and a simulated value are available and need validation, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. There is no explicit reference to sibling tools like pcb_validate_with_openems.

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