gitee_replace_pull_labels

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

With no annotations, the description must fully disclose behavior. 'Replace all labels' implies deletion of existing labels and addition of new ones, but it does not mention required permissions, side effects (e.g., which labels are removed), or the return value. The description is too terse to provide adequate transparency.

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 extremely concise (7 words in one sentence). It is front-loaded with the core action. However, this brevity sacrifices valuable context that could be added without losing conciseness.

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 lack of output schema and annotations, the description should include behavioral context such as that it replaces all existing labels, how labels are matched, and what happens on error. The current description leaves the AI agent without enough information to invoke the tool correctly in varied scenarios.

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% with clear parameter descriptions (e.g., 'labels' as 'JSON array of label names'). The description adds no extra meaning beyond the schema, which is the baseline expectation. No parameter details are missing, but the description could provide a usage example.

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 'Replace all labels on a pull request' clearly states the action (replace) and the resource (labels on a pull request). However, it does not differentiate from sibling tools like 'gitee_add_issue_labels' or 'gitee_delete_pull_label', missing a chance to clarify that it replaces all existing labels rather than adds or removes individually.

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 on when to use this tool versus alternatives such as 'gitee_add_pull_label', 'gitee_delete_pull_label', or 'gitee_replace_issue_labels'. There is no mention of prerequisites, typical use cases, or when not to use it.

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