github_issues_remove_label

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

Without annotations, the description solely states the action, failing to disclose behavioral traits like whether the label must exist, authorization requirements, or side effects. The burden is high but unmet.

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 clear sentence, concise and to the point. However, it could be slightly more structured or include brief context.

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 description is minimally complete for a simple operation, but lacks context about prerequisites (e.g., issue must exist, label must be applied) and does not reference sibling tools for clarity.

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 100%, but the parameter descriptions are trivial (just repeating names). The tool description does not add any extra meaning beyond the schema, so a baseline score 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?

The description 'Remove a label from an issue' clearly states the action and resource, but does not differentiate it from similar sibling tools like github_issues_remove_all_labels or github_issues_set_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?

The description provides no guidance on when to use this tool versus alternatives, such as github_issues_remove_all_labels for removing all labels or github_issues_set_labels for replacing labels.

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