pcb_manage_rule_config

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

Annotations already declare destructiveHint=true and non-idempotent, so the safety profile is covered. The description adds real value beyond them by disclosing an upstream EDA bug (pro-api-sdk #34) where saved rule changes read back correctly but do not affect pour reflow until document reopen — a behavioral caveat an agent could not get from structured fields.

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 action list is compact and front-loaded, one line per action with its parameters in parentheses. The final bug warning is long but earns its place because it changes how the agent should sequence save/reflow work. No filler sentences.

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?

For a nine-parameter multi-mode tool with a nested, structurally undocumented ruleConfiguration object and no output schema, the definition covers action semantics and the reflow caveat but says nothing about what the get_* actions return or what shape a rule configuration must take for save. That gap matters most for the save action.

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 100%, so all nine parameters (including the action enum) are already documented in the schema, largely duplicating the description's '(configurationName)', '(for rename)', etc. The per-action grouping adds modest organizational value, but the nested ruleConfiguration object is described only as 'Rule config object' with an empty properties map, so the description does not compensate for that opacity.

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?

States a specific verb+resource (managing DRC rule configurations) and enumerates all eight actions with their inputs, which is far more informative than a generic 'manage' label. It does not, however, distinguish itself from nearby siblings like pcb_get_design_rules or pcb_manage_net_rules, leaving an agent to infer that 'rule configuration' is a stored config set rather than design/net rules.

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 action-to-parameter mapping implicitly tells the agent how to invoke each mode, and the reopen warning implies a post-save workflow. But there is no explicit when-to-use guidance, no statement of when to prefer this over pcb_manage_net_rules or pcb_get_design_rules, and no prerequisites for destructive actions.

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