PATCH /statuslabels/{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 structurally. The description adds only the vague 'selected fields' phrasing; it never says that omitted fields are left untouched, what the destructive risk is, or that a confirmation string may be required — nothing beyond what annotations and schema already state.

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 front-loaded and efficient. The second sentence ('Generated from Snipe-IT OpenAPI operation statuslabelsid-3') is generator boilerplate that tells an agent nothing actionable, so the description is not entirely earning its space.

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 mutation with a nested six-field body, a conditional confirm requirement, and no output schema, the description leaves out the body field meanings, the confirm gate, and any statement of effect. Given the tool's complexity and the sibling-name ambiguity, an agent cannot call it confidently from this text alone.

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 33% and the body is a nested object with six undocumented properties (name, type, color, notes, show_in_nav, default_label). The description does not name or explain any parameter, so it fails to compensate for the coverage gap. The only schema-side help is the confirm field's own description.

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?

The description names a clear verb ('Updates') and resource ('a status label', with the /statuslabels/{id} path), so an agent knows it is a partial-update mutation. It gives no differentiation from the near-identical siblings (snipeit_gen_statuslabelsid, _1, _2, plus the PUT/GET variants), which matters here given how many similarly named status-label tools exist.

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 guidance on when to use this PATCH partial-update versus the sibling status-label update/get tools, and no mention of prerequisites such as the confirm=YES gate or permissions. 'Updates selected fields' is the only usage signal, and it is inferential rather than explicit.

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