replace_issue_labels

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

With no annotations, the description carries full burden. It explicitly states that every existing label is removed and only the listed ones remain, and warns about the destructive nature. Could mention potential errors for non-existent labels, but overall transparent.

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 sentences, front-loaded with the primary action, no wasted words. Every sentence adds value: first declares the purpose, second gives usage warning.

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 parameter count (4), 100% schema coverage, and no output schema, the description is mostly complete. It explains replacement behavior and cautions. Could detail return values or error handling, but reasonable for a replacement tool.

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 100%, so baseline 3. The description adds meaning by clarifying that 'labels' is an array of names used for full replacement, and that the operation removes all existing labels. This goes beyond the schema's generic 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 uses a strong verb 'REPLACE' and specifies the exact resource 'issue's ENTIRE label set'. It clearly distinguishes itself from sibling tools like add_issue_labels, remove_issue_label, and clear_issue_labels by emphasizing that it replaces all labels at once.

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?

Explicitly advises reading current labels first to preserve any that must survive and to confirm with the user before replacement. This provides clear when-to-use and when-not-to-use guidance, differentiating from partial modification tools.

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