remove_issue_label

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

Adds value beyond annotations by clarifying it detaches the label reference and does not delete the label definition. Aligns with idempotentHint and destructiveHint annotations.

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 concise sentences with no fluff, immediately stating the action and key behavioral distinction. Front-loaded and efficient.

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 and presence of schema/annotations, the description provides sufficient context. Could include an example or clarify exactly what to pass for label, but not essential.

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 covers 100% of parameters but descriptions are generic ('a string that will be trimmed'). Description does not add parameter-specific meaning; baseline of 3 is appropriate.

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?

Clearly states it removes a label from a Huly issue and distinguishes from deleting the label definition. Differentiates from sibling add_issue_label.

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?

Implies use for removing a label but does not explicitly specify when to use versus alternatives or provide exclusions. No direct comparison to add_issue_label or other tools.

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