POST /models/{id}/files

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false, openWorldHint=true), it discloses the decisive behavioral fact that the server expects multipart/form-data while this tool sends JSON because the vendored spec declares JSON, so the call will fail. That is exactly the kind of runtime trait annotations cannot express.

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?

Four short sentences, with the capability and the failure warning front-loaded. The leading "POST /models/{id}/files:" restates the title, a minor redundancy, but no sentence is 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 mutate tool with annotations covering safety and a schema covering required fields, the description supplies the missing pieces an agent needs: the tool is non-functional for its stated purpose and where to go instead. No output schema exists, but the outcome (failure) is made explicit.

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 67%; id and confirm are documented in the schema, but the nested body requires file and the optional notes carry no descriptions anywhere. The description only loosely hints at the file payload ("Upload one or more files") and says nothing about notes or the JSON-vs-multipart mismatch per parameter, so it adds little 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 (upload one or more files to a model) and names the endpoint path. It is separable from siblings like snipeit_gen_modelsidfilesfile_id or snipeit_gen_hardware_upload_files by the model-scoped resource, though it never explicitly contrasts them.

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?

It explicitly tells the agent not to use this tool and redirects to a concrete alternative: upload files in the Snipe-IT web UI. That is a clear when-not-to-use plus a substitute, which is the strongest form of routing guidance.

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