Read native PCB design rules

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Does not mutate the board' largely restates structured data. The description adds nothing about how the different scopes behave, whether results are cached/live, what idempotentHint=false means for repeated reads, or how timeoutMs affects the call.

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?

Two short sentences with the core purpose front-loaded and no filler. The second sentence is largely redundant against the annotations, costing a little efficiency but not clarity.

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 no output schema, zero schema description coverage, and a five-value enum whose members are undocumented, the description is too thin for an agent to pick a scope confidently or understand what comes back. It covers the safety profile only because annotations already do.

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% for both parameters, so the description must carry the burden and does not. It gestures at 'current or configured scopes' but never explains netRules, netByNetRules, or regionRules, and timeoutMs is not mentioned at all.

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 and resource: 'Read native EasyEDA Pro PCB design rules', scoped to 'current or configured scopes'. This clearly separates it from easyeda_run_drc (which executes checks) and easyeda_prepare_drc_edit (which edits rules). However, it never names those siblings explicitly, so the differentiation is inferred rather than stated.

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 phrase 'for current or configured scopes' implies a read-inspection use case, but there is no explicit when-to-use guidance, no prerequisites, and no statement about when to prefer easyeda_run_drc or the DRC edit tools instead. An agent must infer the workflow position from the name alone.

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