gitee_get_org_membership

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

No annotations are provided, so the description must fully cover behavioral traits. It only states 'Get a member's organization membership' without disclosing what the membership entails (e.g., role, state, permissions), error behavior (e.g., if user is not a member), or read-only nature. This is insufficient for a tool with no annotations.

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, short sentence with no unnecessary words. It is appropriately concise for a simple getter tool, though it could benefit from slightly more detail 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?

No output schema is provided, so the description should clarify what the return value includes (e.g., member role, state). It does not mention error handling or edge cases (e.g., non-existent user). For a membership retrieval tool, this is incomplete.

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 descriptions for both parameters ('Organization path' and 'Username'). The description adds no further meaning beyond the schema. Baseline 3 is appropriate as the tool description does not enhance parameter understanding.

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 (Get) and resource (a member's organization membership). It distinguishes from siblings like gitee_get_my_org_membership (current user) and gitee_list_org_members (list of members) through the specific wording. However, it could be slightly more explicit about requiring a username.

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. For example, it does not clarify that this is for a specific user by username, while gitee_get_my_org_membership is for the authenticated user. The description lacks any selection criteria.

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