pcb_analyze_copper_spreading

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

With no annotations provided, the description must fully disclose behavioral traits. It merely says 'analyze' without stating whether this is a read-only calculation, what assumptions are made, how results are presented, or any side effects. This is a significant transparency gap.

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 only one sentence, which is overly terse. It lacks the minimal detail needed to understand the tool's function, making it under-specification rather than concise. There is no structured information beyond a single vague clause.

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?

Given the 4-parameter schema, no annotations, and no output schema, the description is far from complete. It does not explain the model, expected inputs, output format, or any caveats, making the tool essentially unusable based on the description alone.

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 does not mention or explain any of the four parameters. Although parameter names like 'power_watts' and 'copper_area_mm2' are somewhat self-explanatory, the description fails to compensate for the complete lack of parameter documentation, leaving the agent without critical context about units, relationships, or defaults.

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 'Analyze copper area heat spreading' clearly uses the verb 'analyze' with the resource 'copper area heat spreading', which distinguishes it from other PCB analysis tools focused on different phenomena. However, it lacks specificity about the exact analysis or output, making it slightly vague.

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 guidance on when to use this tool compared to alternatives such as pcb_analyze_thermal or pcb_analyze_thermal_via. It does not state conditions, prerequisites, or exclusions, leaving usage context entirely implicit.

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