DELETE /locations/{id}

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it never mentions irreversibility, whether the delete is soft or hard, cascading effects on assets assigned to the location, or the SNIPEIT_CONFIRM_WRITES gating that the schema implies.

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?

The first sentence is tight and front-loaded. The second sentence, 'Generated from Snipe-IT OpenAPI operation locationsid-2,' is metadata noise that occupies half the description without adding meaning for an agent.

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?

A destructive mutation with no output schema and a confirmation parameter deserves at least a note on consequences and the confirm flow. The description leaves both unaddressed, so an agent calling it correctly depends entirely on inferring behavior from annotations and the raw schema.

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 50%: `confirm` is documented in the schema, but `id` has no description. The description does not compensate at all — it never explains what the id refers to (location ID vs. any other identifier) or how the confirm string interacts with environment configuration.

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: 'Deletes a location.' An agent can tell what the tool does. However, it does not distinguish itself from the many sibling location tools (snipeit_gen_locationsid, snipeit_gen_locations_1/2/3, snipeit_get_location, snipeit_list_locations), so the agent cannot confirm this is the delete variant of locations without reading the raw path.

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 when-to-use guidance, no prerequisites, no mention of alternatives. With a dozen-plus location-related siblings and a separate generic snipeit_raw_request, the description gives the agent nothing to route on besides the name itself.

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