List schematic components

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description need not repeat that. It adds useful behavioral context by detailing the returned device identity fields and mentioning 'place_component deviceItem in this project', which helps the agent understand the tool's role in cloning operations.

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 sentence that front-loads the core function and lists fields efficiently. However, the inline list could be more readable with line breaks or bullet points. It earns its place with no wasted words.

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 presence of an output schema, the description does not need to explain return values in detail, but it does. However, it misses important context about pagination (limit/offset) and lacks guidance on usage among sibling tools. It is adequate for a straightforward listing tool but not comprehensive.

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% (only projectId described). The description does not explain the limit and offset parameters, which are critical for pagination. Without elaboration, the agent cannot understand how to control the number of results or page through them.

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 that the tool lists schematic components, and enumerates the specific fields returned (primitiveId, reference, value, footprint, x/y/rotation, device identity for cloning). This specificity distinguishes it from sibling tools like easyeda_schematic_component_pins or easyeda_pcb_components.

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 provides no guidance on when to use this tool versus alternatives, nor does it specify exclusions or prerequisites. Among many schematic tools, the agent receives no help in selecting this one over others like easyeda_schematic_nets or easyeda_schematic_place_component.

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