kicad.search_footprints

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

No annotations provided, so description carries full burden. Fails to disclose search semantics (fuzzy vs exact matching, which fields are searched) or performance characteristics. The example 'QFP-48' hints at search capability but doesn't explain behavior.

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?

Two sentences with purpose front-loaded followed by an example. No redundant text, though brevity comes at the cost of parameter documentation given the empty schema descriptions.

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 three parameters, zero schema descriptions, and no annotations, the description should explain parameter semantics, particularly the library filter. Relies entirely on the output schema for return value documentation, which is acceptable, but leaves input parameters under-documented.

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 has 0% description coverage. The description provides an example showing query='QFP-48' and limit=10, which partially compensates for those two parameters. However, the 'library' parameter (which filters by library name) is completely undocumented with no hint about valid values or default behavior.

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?

States a clear verb-object pair (search footprints) and scope (KiCad libraries). Distinguishes from sibling 'list_footprints' by implying filtered retrieval vs enumeration, though it doesn't explicitly clarify this distinction.

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?

Provides no guidance on when to use this versus 'list_footprints' or 'search_symbols'. Does not mention that the library parameter can filter to specific libraries or that empty string searches all libraries.

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