List schematic components

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds that components are 'normalized' and which fields are present, which is useful context, but it says nothing about pagination, truncation, or the cost of a full enumeration despite limit/allPages parameters.

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 filler; every clause carries information. It is efficient, though its brevity is partly the source of the missing parameter and usage guidance.

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 five optional parameters, no output schema, and only 20% schema description coverage, the definition leaves the agent guessing about pagination defaults (allPages=true), the meaning of includeRaw, and how limit interacts with full listing. For a list tool with this many knobs, more explanation is required.

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 20%: just the 'query' parameter is documented, while limit, allPages, timeoutMs, and includeRaw have no descriptions in either the schema or the tool description. The description's field list refers to return values, not inputs, so it does not compensate for the coverage gap.

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 gives a specific verb and resource ('Lists normalized schematic components') and enumerates the returned fields (designator, value/name, footprint, position, key properties), so an agent knows exactly what comes back. It does not explicitly contrast itself with easyeda_list_pcb_components or easyeda_find_component, so sibling differentiation is left implicit.

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?

There is no statement of when to use this listing tool versus easyeda_find_component, easyeda_schematic_snapshot, or easyeda_get_schematic_nets. No prerequisites, no exclusions, and no guidance on whether this is a full-enumeration tool or a filtered lookup.

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