get_design_rules

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

With no annotations provided, the description carries the burden of conveying safety. The verb 'Read' signals a non-mutating operation, which is helpful. However, it adds no details about side effects (or lack thereof), required permissions, or whether the tool validates the XML. The description is competent but minimal.

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?

A single, front-loaded sentence with no redundant words. It immediately states the action and resources. Perfectly sized for the simplicity of the tool.

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 simple tool (one optional param, output schema present), the description covers the core purpose. However, the lack of parameter guidance and usage differentiation leaves noticeable gaps for an agent trying to decide whether and how to invoke this tool.

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 only parameter 'path' has no schema description (0% schema coverage), and the tool description does not explain what path refers to beyond the indirect hint 'from DipTrace XML'. It does not clarify whether path is a filesystem path a document ID, or an XML fragment, nor how the optionality works. The description fails to compensate for the lack of parameter documentation.

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 ('Read') and names the exact resources ('PCB DRC/routing rules or schematic ERC settings') plus the source ('DipTrace XML'). This clearly distinguishes it from sibling tools like run_drc or run_erc, which execute checks rather than read settings.

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 implies when to use the tool (when you need to read design rules from DipTrace XML) but provides no explicit guidance versus alternatives such as get_document_info, read_xml_fragment, or the run_drc/run_erc siblings. No exclusions or alternative tool names are mentioned.

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