gitee_get_enterprise_member

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

No annotations are provided, so the description bears full responsibility for disclosure. It states 'Get enterprise member information' but does not describe what information is returned, whether the operation is read-only, any required permissions, or potential rate limits. This lack of detail could lead to misuse.

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, consisting of a single sentence. It efficiently conveys the core purpose without unnecessary words. However, it could include more detail without sacrificing conciseness, such as specifying that it returns information for a single member.

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 presence of sibling tools for listing and searching enterprise members, the description lacks specificity about its scope (single member lookup). There is no output schema, so the description could hint at the return format. The description is minimally viable but could be improved to provide full context.

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 clear descriptions for both parameters ('Enterprise path' and 'Username'). The description adds no additional context beyond the schema. Since the schema already defines the parameters adequately, a baseline score 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 'Get enterprise member information' clearly indicates the action (get) and resource (enterprise member). It implies retrieving a single member's details, especially given the required 'username' parameter. However, it does not explicitly differentiate from sibling tools like gitee_list_enterprise_members or gitee_search_enterprise_members, which could cause ambiguity.

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. For example, it does not mention that this tool is for fetching a specific member by username, whereas list_enterprise_members is for listing all members. An agent would benefit from explicit instructions on tool selection.

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