project_manage_labels

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

Annotations already indicate destructiveHint=false, and the description aligns with that. However, beyond the annotations, the description does not disclose potential side effects (e.g., whether missing labels are created, error behavior, or permission requirements). The bar is lower due to annotations, but the description adds no extra behavioral context.

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 sentence with no redundant words. It is front-loaded and efficiently conveys the tool's purpose. Every word earns its place.

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 low complexity (4 parameters, 2 required, no output schema), the description is adequate but lacks usage guidance and behavioral nuance (e.g., relationship between addLabels and removeLabels, order of operations). It is minimally complete but could be more helpful with explicit context.

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%, so the schema already documents each parameter (e.g., 'Labels to add', 'Labels to remove'). The tool description adds no additional meaning beyond the schema, meriting the baseline score of 3.

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 'Add or remove labels on an issue' clearly states the verb (add/remove) and resource (labels on an issue). It effectively distinguishes from siblings like project_edit_issue or project_manage_assignees by focusing specifically on label manipulation.

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 explicit guidance is provided about when to use this tool vs alternatives (e.g., project_edit_issue). The description implies label-only operations but does not state prerequisites, when-not-to-use, or context. This omission leaves the agent without clear decision criteria.

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