Find EasyEDA Pro component

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description does not add further behavioral details (e.g., search scope, return format, or pagination). With annotations covering the basics, a score of 3 is appropriate.

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 purpose. Every word is necessary; there is no waste.

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 search tool with 3 parameters and no output schema, the description is adequate but leaves gaps: it doesn't explain whether results are returned in a list, what properties are included, or behavior when multiple matches occur. More context would aid the agent, but the essentials are covered.

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 coverage is only 33% (only 'query' has a description). The description adds no new meaning beyond repeating the schema description for 'query'. Parameters 'limit' and 'timeoutMs' lack any description in both schema and description, so the tool description fails to compensate for the low schema coverage.

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 the verb 'Finds', the resource 'component', and the search criteria (designator, name, value, footprint, or property). It distinguishes this tool from siblings like 'easyeda_find_net' and 'easyeda_trace_component' by specifying the search object and criteria.

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 (e.g., easyeda_list_schematic_components for listing all components, or easyeda_navigate_component for navigation). There are no prerequisites, exclusions, or suggested contexts mentioned.

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