List Footprint Libraries

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

Annotations already declare the operation as read-only and idempotent, and the description adds useful behavioral context: it returns only the first 20 footprints per library and defaults to KiCAD standard install paths. This explains the partial listing behavior and search scope beyond the safety profile.

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 concise sentences with no wasted words; the verb and scope are front-loaded. It efficiently communicates the tool's purpose and default behavior.

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?

The tool is simple, has an output schema, and annotations cover side-effects. The description covers the key behavioral details (library type, truncation, default paths). Minor omission: no explicit pointer to sibling tools for full footprint listing, but not required given the output schema and annotations.

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?

The schema fully describes searchPaths with clear meaning ('directory that contains .pretty subdirs'), and the description complements it by explaining the default behavior ('Searches KiCAD standard install paths by default') that searchPaths overrides. This adds context beyond the schema alone.

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 states a specific verb ('List') and resource ('available .pretty footprint libraries and their contents'), with a clear scope ('first 20 footprints per library'). This distinguishes it from sibling tools like list_library_footprints, which lists footprints for a specific library, and list_libraries, which may list all library types.

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 gives clear context: it searches KiCAD standard install paths by default and can be overridden via searchPaths. It does not explicitly name alternatives or exclusions, but the context is sufficient for an agent to understand when this tool is appropriate. Could be improved by stating when to prefer this over list_library_footprints.

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