gitee_remove_collaborator

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

With no annotations, the description carries the full burden, but it only states 'Remove a collaborator' without disclosing effects (e.g., irreversible, requires admin rights, impact on repo access). This is insufficient for a destructive operation.

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 too brief (3 words) and lacks structure. While concise, it sacrifices necessary context. A single sentence with more detail would improve comprehension without losing brevity.

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 completely inadequate for a tool with 3 required parameters and no output schema. It does not explain return values, prerequisites, or edge cases, making it hard for an agent to use correctly.

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 the baseline is 3. The description adds no parameter-specific information beyond the schema's descriptions of 'owner', 'repo', and 'username', which are self-explanatory.

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 collaborator' clearly states the action and resource, distinguishing it from siblings like 'gitee_add_collaborator' and 'gitee_check_collaborator'. However, it does not specify the scope (e.g., repository), which could be inferred from parameters but is not explicit.

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_remove_org_member' or 'gitee_remove_enterprise_member'. There is no mention of prerequisites, permissions, or when not to use.

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