remove_label

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

There are no annotations, so the description must carry the full burden of disclosing behavior. It states the core mutation ('Remove a single label') but does not mention authentication requirements, what happens if the label is not present, error behavior, or any side effects. For a mutating operation with no annotation support, this is insufficient.

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 a single focused sentence that immediately states the action and resource, followed by a docs link. Every part earns its place, and there is no redundant or filler content.

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?

Given the tool's simplicity, the description is minimally adequate: it names the operation and resource, and the schema fully documents parameters. However, it omits usage guidance and edge-case behavior (e.g., missing label, multi-label removal), which would make it more complete for an agent deciding how to invoke it.

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?

The input schema already provides complete descriptions for all 4 parameters (100% coverage), so the baseline is 3. The description adds no extra meaning to the parameters beyond what the schema already states, but it does not need to given the high schema coverage.

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 uses a specific verb ('Remove') and clearly identifies the resource ('a single label from a GitHub issue'), making the tool's purpose unambiguous. It also naturally distinguishes itself from sibling tools like add_labels or list_labels, which perform different operations on labels.

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 is provided about when to use this tool versus alternatives. For example, it does not mention that add_labels should be used for adding labels, or that this tool removes only one label at a time. The docs link offers external help but the description itself provides no usage context.

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