snipeit_gen_departments_1Creates a new department in Snipe-IT through the API; provide the department name and include YES confirmation when write confirmation is enabled.
POST /departments: Create a department. Generated from Snipe-IT OpenAPI operation departments-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 disclose the destructive, non-idempotent, open-world write profile, and the description adds nothing beyond that. It omits the SNIPEIT_CONFIRM_WRITES confirm="YES" requirement, which is central to actually completing this write.
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 with the action front-loaded, but 'POST /departments' duplicates the title and the OpenAPI provenance note adds no actionable information.
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 create operation with a nested body and a confirm gate, the description should explain the write-confirmation behavior and what a successful create yields. With no output schema and half the parameters undescribed, it is under-specified.
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 coverage is only 50% and the description contributes zero parameter meaning, neither the required body.name field nor the confirm gate. An agent must rely entirely on the schema, which leaves part of the surface undocumented.
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 department'), so the operation is immediately identifiable. It offers no differentiation from the many sibling department tools (edit, get, delete), leaving the agent to infer scope.
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 indication of when to use this versus snipeit_gen_departments_edit or the generic snipeit_raw_request, nor any prerequisites such as the confirm flag. Usage is only implied by the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.