Add and remove issue labels in a single call to keep the label set standard-compliant, such as swapping area/old for area/new without interim invalid states.
Add and remove labels in one operation. The resulting set must satisfy the standard, so swap an area with add=['area/new'], remove=['area/old'] in one call.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| add | No | ||
| remove | No |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It discloses that add and remove happen in one operation and that the resulting set must satisfy a constraint, but it omits permission requirements, failure behavior, idempotency, and return semantics.
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 description is two tightly written sentences with the core operation front-loaded and an example that immediately illustrates usage. There is no wasted text.
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?
The tool is a mutation with no annotations, no output schema, and 0% parameter description coverage. The description explains the central add/remove behavior but leaves id semantics, return values, and error behavior unaddressed.
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 0%, so the description must compensate. It clarifies add and remove with an example label format and the swap pattern, but does not explain the required id parameter or fully define label validity.
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 states a clear specific operation: adding and removing labels in one call. It identifies the resource (labels) and the combined add/remove behavior, but does not differentiate itself explicitly from any sibling tool or name the target entity.
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 provides a concrete usage scenario for swapping labels atomically with add and remove in one call. However, it does not state when not to use it or name any alternative tool or approach.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.