add_via

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

The description only states it adds a via, which aligns with annotations (not read-only), but does not disclose side effects, permissions required, or behavior if x/y are invalid. Annotations already indicate non-destructiveness, but the description adds minimal behavioral context.

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 concise: a single-purpose sentence followed by a clear parameter list with no extraneous 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?

The description covers the basics of the tool's action and parameters, but lacks context on return values (though output schema exists), constraints, or integration with other tools. Adequate but not thorough.

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?

With 0% schema description coverage, the description compensates by explaining each parameter (e.g., units for size/drill, default layers, net number). This adds meaning beyond the schema property titles.

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 'Add a via at a position' clearly states the verb 'Add' and resource 'via', making the tool's purpose specific and distinct from sibling tools like 'add_copper_zone' or 'add_global_label'.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'add_thermal_vias'). It does not mention prerequisites, constraints, or when not to use it.

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