DELETE /models/{id}

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond that — it doesn't say whether this is a soft delete, what happens to models still assigned to assets, or what a successful response looks like.

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?

Two short sentences, front-loaded with the verb and resource. The second sentence is generator boilerplate but does explain the opaque operation slug in the tool name, so it is not pure waste.

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 single-entity delete with no output schema, the definition is minimum viable: annotations carry the safety profile and the schema carries the parameters. It still omits the consequences of deletion and why one sibling (path id variant) should be preferred over another.

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 100%: the 'id' and the conditional 'confirm' parameter (required when SNIPEIT_CONFIRM_WRITES=true) are fully documented in the schema. The description contributes no additional parameter meaning, so the baseline 3 applies.

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: 'DELETE /models/{id}: Delete a model.' An agent knows exactly what it does. However, it offers no differentiation from the similarly named siblings (snipeit_gen_modelsid, _1, _2), which are presumably GET/PUT/PATCH on the same path — the agent must inspect those separately.

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 guidance on when to use this versus snipeit_gen_modelsid_1/_2 or the raw request tool, and no preconditions such as checking for assigned assets before deleting a model. The only signal is the destructive annotation, not the text.

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