pdn_recommend_decoupling_caps

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

Annotations are empty, so the description must carry the full burden. It only states that the tool uses a 'simple PDN heuristic' to make recommendations, without disclosing side effects (e.g., whether it modifies the design), the nature of the recommendations, or limitations. It does not contradict annotations, but it provides 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 a single sentence that is front-loaded with the action ('Recommend') and avoids redundant wording. It is concise, though it sacrifices necessary detail for brevity.

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 has four parameters with zero description coverage and no explanation of prerequisites or expected output. Even with an output schema present, the description fails to provide enough context for an agent to correctly invoke the tool, especially given overlapping sibling tools.

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 explain any of the four parameters (ic_refs, vcc_net, supply_voltage_v, target_ripple_mv). The description adds no meaning beyond the schema's field names, leaving the agent without guidance on required inputs or their formats.

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 uses a specific verb ('Recommend'), identifies the resource ('local and bulk decoupling'), and method ('simple PDN heuristic'). It clearly states what the tool does, but does not distinguish it from sibling tools like si_calculate_decoupling_placement or emc_check_decoupling_placement, which may also provide decoupling recommendations.

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. Sibling tools such as si_calculate_decoupling_placement, emc_check_decoupling_placement, and pcb_place_decoupling_caps overlap in purpose, but the description lacks selection criteria, prerequisites, or exclusions.

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