lib_create_footprint

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

No annotations are provided, so the description carries the full burden and does not meet it. It does not say whether an active library must already be loaded, whether the new footprint is created empty (requiring lib_add_footprint_pad etc. afterwards), what happens on a name collision, or whether the creation is persisted or reversible.

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 core sentence is front-loaded and the whole definition is short. The Args/Returns scaffolding adds little value given the schema and output schema exist, but the total length stays tight enough not to burden the reader.

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 mutation tool with no annotations, this is under-specified: the return value is covered by an output schema, but the description omits prerequisite state (active library), post-creation workflow (adding pads, saving), and failure modes. An agent could call it and be surprised by the result.

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 0%, so the description must compensate, but the Args block only repeats the schema titles ('Footprint name', 'Footprint description') with no naming conventions, constraints, or default/exclusion behavior. Effectively zero information is added beyond the structured fields.

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 specific verb and resource ('Create a new PCB footprint') plus scope ('in the active library'), which is more than a restatement of the name. However, it gives no differentiation from near-identical siblings such as lib_create_standard_footprint and lib_create_footprint_from_package, so an agent cannot tell from the text which creator to pick.

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 when-to-use guidance, no exclusions, and no mention of the alternatives among the many sibling creation tools. The only contextual hint is 'active library', which is a scope statement rather than a usage rule.

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