add_thermal_vias

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

Annotations are sparse (all false), so description should disclose behavior. It mentions auto-selection of pad_number and net_name but fails to state that the tool modifies the PCB file, required permissions, or side effects. Lacks full 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?

Description is structured as a docstring with parameter list, but is somewhat lengthy. The first sentence is concise, but the parameter block could be trimmed. It earns its place but not optimally concise.

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 9 parameters and no output schema shown, description explains parameters but omits return value, error conditions, and preconditions (e.g., pad must exist). Adequate but incomplete for a mutation 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 has 0% description coverage, so description compensates with parameter explanations (e.g., 'center vias on', 'auto-selects largest SMD pad'). Adds meaning beyond schema, though some parameters like rows/cols are self-explanatory.

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?

Description clearly states 'Add a grid of thermal vias under a footprint pad', specifying the action and resource. This distinguishes it from siblings like 'add_via' (single via) and zone 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?

Description implies usage (thermal vias under a pad) but does not explicitly state when to use versus alternatives (e.g., add_via for single vias). No when-not or alternative guidance provided.

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