snipeit_gen_manufacturers_1Creates a new manufacturer record in Snipe-IT from a required name, so you can tag assets to that vendor. Requires confirm "YES" when write confirmation is enabled.
POST /manufacturers: Create a manufacturer. Generated from Snipe-IT OpenAPI operation manufacturers-1.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | ||
| confirm | No | Required when SNIPEIT_CONFIRM_WRITES=true. Exact string "YES" to apply this write. |
Changes observed during successful MCP inspections.
v0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already carry the important behavioral profile (destructiveHint=true, idempotentHint=false, openWorldHint=true), and the description adds nothing to it — no note on what the confirmation gate means, no side effects of creation, no required permission. The single sentence 'Create a manufacturer' merely restates the endpoint.
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?
Very short and front-loaded, but half the text is redundant boilerplate ('POST /manufacturers' repeats the title, and 'Generated from Snipe-IT OpenAPI operation manufacturers-1' is noise). No wasted length, but also no earned content.
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 destructive, non-idempotent creation endpoint with no output schema, the description should say at minimum what is created (required name field), what the confirmation gate implies, and what a successful call returns gives the new ID. None of that is present.
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 only 50% and the description mentions no parameters at all. It does not tell the agent that body.name is the required field or that confirm must be the exact string "YES" when SNIPEIT_CONFIRM_WRITES is enabled, leaving the description to add zero meaning beyond the schema.
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 manufacturer'. However, it offers no differentiation from sibling manufacturer endpoints (snipeit_gen_manufacturers, snipeit_gen_manufacturersid, snipeit_gen_manufacturersid_1/2/3), which are indistinguishable by name alone.
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?
No indication of when to use this versus snipeit_raw_request or the other manufacturer endpoints, and no prerequisites mentioned. The agent must infer that this is the write path for creating rather than reading or updating manufacturers.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.