gitee_search_enterprise_members

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

No annotations exist to indicate safety (e.g., readOnlyHint), and the description does not disclose any behavioral traits such as authentication requirements, rate limits, or side effects. The tool appears to perform a read operation, but this is not explicitly stated.

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 very concise (two words) but could be considered under-specified. It is not verbose but lacks essential context. For a simple search, it is adequate but not exemplary.

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, and the description does not explain what fields are returned or how pagination works. Given the context of a search tool, the agent needs to understand the response format to use the output effectively.

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%, so the schema already documents all parameters. The description adds no additional meaning beyond the schema. A baseline of 3 is appropriate as it does not degrade but also provides no extra insight.

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 'Search enterprise members' clearly states the verb and resource. However, it doesn't differentiate from the sibling 'gitee_list_enterprise_members' which also lists members. A more specific description could clarify that this tool filters results by keyword.

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 vs alternatives like 'gitee_list_enterprise_members'. The agent cannot infer from the description alone whether to use search or list.

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