gitee_delete_project_labels

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

No annotations provided, so the description bears full burden. It only states 'Delete project-level labels' without disclosing destructive nature, potential side effects (e.g., removing labels from issues), permissions required, or batch deletion behavior. Critical behavioral context is missing.

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 (only 3 words), but this is under-specification rather than conciseness. For a tool with 3 required parameters and no annotations, more detail is necessary to be useful. Slightly more informative sentences would improve without losing efficiency.

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 is inadequate. It does not explain the operation's effect, error cases, or how it relates to sibling delete-label tools. An agent cannot reliably select or invoke this tool based on the description alone.

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?

Input schema has 100% description coverage for all three parameters. The description adds no additional meaning beyond what the schema provides. For example, the 'labels' parameter expects a JSON array, but the description does not elaborate on format or behavior.

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 'Delete project-level labels' clearly states the verb (Delete) and the resource (project-level labels). It distinguishes from sibling tools like gitee_delete_label (repo-level) and gitee_delete_issue_label (issue-specific), but could further clarify that 'project-level' refers to labels associated with the repository itself, not individual issues.

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 on when to use this tool versus alternatives. Siblings include gitee_delete_label, gitee_delete_issue_label, and gitee_delete_pull_label, but the description does not differentiate use cases or provide any when-to-use/when-not-to-use criteria.

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