firmware_packages

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

No annotations are provided, so the description carries the full disclosure burden. 'List' implies a read-only operation and the description adds that content comes from the local repository and feeds project generate, but it says nothing about return contents (names/versions?), performance of a filesystem scan, or behavior when the repository override is invalid.

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?

One sentence, front-loaded with the verb and resource, and the parenthetical earns its place by linking the output to a downstream operation. No filler.

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 zero-required-parameter read-only listing with no output schema, the definition says enough to select and call it correctly. It could go further by sketching what each listed package entry contains or how it differs from pack_status, but nothing essential is missing.

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 100% and the single optional 'repository' parameter is fully documented in the schema as an override path. The description adds only the notion that the default is the 'local repository', which is marginal added meaning — baseline 3 is correct.

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 ('List') and resource ('installed STM32Cube firmware packages in the local repository'), with useful scoping ('local repository'). It does not explicitly contrast itself with nearby siblings like pack_status or template_list, so an agent still has to infer the boundary.

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 parenthetical 'these are what `project generate` copies Drivers from' implicitly tells the agent when this list matters before generating code, but there is no explicit when-to-use/when-not guidance or named alternative (e.g., pack_status for versions/enablement).

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