Find EasyEDA Pro net

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

The description is consistent with the readOnlyHint annotation, indicating no side effects. It adds minor context about return type (connections or metadata) but does not disclose additional behavioral traits beyond the annotations. With annotations already declaring it safe, the description provides marginal added value.

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 concise sentence that front-loads the action and resource. It is efficient but lacks structured breakdown of parameters or usage scenarios. Every word serves a purpose.

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 3 parameters and no output schema, the description does not explain what exactly is returned (e.g., net details, pin numbers, connectivity graph). It does not specify search behavior (partial match, case sensitivity). For a search tool, this is incomplete.

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 only 33%, with only the query parameter having a description. The description does not explain the limit or timeoutMs parameters (default values, max, etc.) despite the low coverage. It does not compensate for the schema gaps.

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 clearly states it finds a net by name and returns connections or metadata. It distinguishes itself from sibling tools like easyeda_trace_net (which likely traces all connections) and easyeda_find_component. However, 'available connections or metadata' is slightly vague but still conveys the main purpose.

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 on when to use this tool versus alternatives such as easyeda_trace_net or easyeda_find_unconnected_pins. The description does not provide context for when to use this tool or any prerequisites.

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