gitee_list_my_org_memberships

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

Without annotations, the description should clearly indicate that this is a read-only, non-destructive operation. It does not mention any behavioral traits such as authentication requirements, pagination limits, or any side effects.

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 clear sentence that conveys the core purpose without redundancy. It is appropriately concise and front-loads the key information.

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?

For a simple list operation, the description states the core function. However, it does not describe return data structure or mention pagination behavior, leaving some context missing. With no output schema, additional context about response would be helpful.

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?

The input schema fully describes all three parameters (active, page, per_page) with descriptions. The tool's description adds no additional parameter semantics, so it relies entirely on the schema.

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 clearly states the action (list) and the resource (organization memberships for the authenticated user). This distinguishes it from related sibling tools like gitee_get_my_org_membership (singular) and gitee_list_org_members (listing members of an org rather than user's memberships).

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?

The description lacks usage guidelines such as when to prefer this tool over alternatives like gitee_get_my_org_membership or gitee_list_org_members. No prerequisites or context for use are mentioned.

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