gitee_leave_org

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

No annotations are provided, so the description must convey behavioral traits. It only states the action without disclosing side effects (e.g., losing access to repos, permissions required) or whether the operation is irreversible. For a mutation, this is insufficient.

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 at three words, but it sacrifices necessary information. While it is front-loaded and waste-free, it could include a sentence about the expected membership state or related tools without harming 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?

Despite the tool's simplicity (one required parameter, no output schema), the description lacks contextual completeness. It does not clarify that this action is for the user leaving their own membership, nor does it differentiate from sibling tools like gitee_add_or_update_org_member or gitee_remove_org_member.

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%, and the schema already defines 'org' as a required string with description 'Organization path'. The description adds no additional meaning beyond the schema, so a baseline 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 'Leave an organization' uses a specific verb and resource, clearly indicating the action and target. It distinguishes from sibling tools like gitee_remove_org_member, which likely removes another member, while this tool is for self-leaving.

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 for admins. There is no mention of prerequisites (e.g., must be a member) or exclusions (e.g., owners may not be able to leave).

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