gitee_get_my_org_membership

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

No annotations are provided, so the description alone must disclose behavioral traits. It states a read operation but omits any details about what happens if the user is not a member (e.g., error or empty response), required authentication scope, or any side effects. The description is minimal and does not add value beyond the tool name.

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 concise sentence with no superfluous words. It conveys the essential purpose without waste. Structure is appropriate for the tool's simplicity.

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 tool has one parameter and no output schema, the description is borderline adequate. It states what the tool does but does not hint at the return value format (e.g., membership object, boolean). For a read operation, specifying that it returns membership details or indication of non-membership would improve completeness. Currently, the agent lacks information about the response structure.

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 description coverage is 100% for the single parameter 'org', which already has a description 'Organization path'. The description adds no additional meaning or context about the parameter (e.g., format, example, or what 'path' refers to). According to rules, baseline is 3 when schema coverage is high, so this score applies.

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 identifies the tool's action: retrieving the authenticated user's membership in a specific organization. The verb 'Get' and resource 'membership' are specific, and the phrase 'authenticated user' distinguishes it from sibling tools like gitee_get_org_membership (likely for any user) and gitee_list_my_org_memberships (list all memberships). Purpose is unambiguous.

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 provides no guidance on when to use this tool versus alternatives. Sibling tools like gitee_get_org_membership, gitee_list_my_org_memberships, and gitee_update_my_org_membership exist, but the description does not mention use cases, prerequisites (e.g., being a member), or when to choose this over others.

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