Generate a complete STM32 C project offline from a bundled HAL configuration model, avoiding CubeMX installation and enabling standalone code generation.
Generate a C project (main.c/main.h/MSP/IRQ/Makefile) entirely offline from the bundled HAL config model — no CubeMX installation involved.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Project name override | |
| toolchain | No | Toolchain | Makefile |
| output_dir | No | Destination directory | |
| project_id | No | Project id |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses that generation is offline and lists the produced files, but does not state overwrite behavior, required permissions, side effects on existing files, or what happens if output_dir already contains content.
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 wasted words. The artifact list and offline constraint are compact and useful.
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 description covers what is generated and the offline model, and the schema fully documents parameters. However, for a file-generating tool with no annotations and no output schema, it omits important behavioral context such as overwrite semantics and return behavior, leaving it only minimally complete.
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%, so the schema already documents all four parameters. The description adds no parameter-specific meaning beyond the schema, which is the baseline expectation when schema coverage is complete.
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: generate a C project, with concrete artifacts (main.c/main.h/MSP/IRQ/Makefile) and the offline bundled HAL config model. It does not explicitly distinguish itself from siblings like project_generate or generate_code, so it falls short of a 5.
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 implies an offline generation context but gives no explicit when-to-use guidance, no when-not-to-use conditions, and no named alternatives among the many sibling generation tools. An agent must infer selection from the name and offline note alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.