pcb_analyze_decoupling

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

With no annotations, the description must disclose behavioral traits, but it only gives a vague action. It does not state whether the tool performs read-only analysis, modifies data, what inputs are essential, or what the output will be.

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 sentence, but it is under-specified rather than appropriately concise. It omits essential details about the tool's behavior and parameters, so brevity comes at the cost of usability.

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?

This tool appears to perform a complex analysis, yet the description is extremely vague. With no output schema, no annotations, and partial parameter documentation, an agent cannot determine what the tool returns or how to invoke it correctly.

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 schema covers 50% of parameters, but the description adds no meaning for any parameter. It fails to explain how capacitor values, frequency, or target impedance relate to the analysis, and leaves undocumented parameters without context.

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 states 'Analyze decoupling capacitor placement,' which gives a verb and resource, but 'analyze' is generic and the specific nature of the analysis is unclear. It does not distinguish this tool from sibling pcb_analyze_decoupling_per_ic, which appears to be a more specific variant.

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 such as pcb_analyze_decoupling_per_ic or pcb_analyze_pdn. There are no prerequisites, context, or exclusions mentioned.

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