gitee_list_enterprise_members

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

The description is minimal and does not disclose behavioral traits beyond listing. There are no annotations, so the agent has no information about pagination limits, sorting, or error handling. 'List' implies read-only, but details are missing.

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 (2 words), but it lacks structure. Each sentence should earn its place; here, a single phrase is acceptable but could be expanded slightly with context.

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 5 parameters, no output schema, and multiple siblings, the description is incomplete. It does not explain pagination, filtering via 'role' and 'active', or how it differs from 'gitee_search_enterprise_members'.

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?

All 5 parameters are described in the schema, achieving 100% coverage. The description adds no extra meaning beyond the schema, so it meets the baseline score for high coverage.

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 'List enterprise members' is a clear verb+noun pairing, but it does not differentiate from the sibling tool 'gitee_search_enterprise_members'. Without additional context, an agent might struggle to choose between the two.

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 usage guidance is provided. The description does not mention when to use this tool instead of 'gitee_search_enterprise_members' or 'gitee_get_enterprise_member', leaving the agent to infer based on parameter differences.

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