gitee_get_enterprise_labels

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

With no annotations, the description bears full burden for behavioral disclosure, yet it only states 'List enterprise-level labels'. It omits details about pagination behavior, default values for page/per_page, sorting, error handling, or what happens if the enterprise doesn't exist.

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, clear sentence without wasted words. However, it could be slightly more informative without losing conciseness (e.g., noting pagination).

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 lack of output schema and annotations, the description is insufficient. It doesn't explain the scope (enterprise vs org/repo), response format, or any constraints. It is minimal and leaves the agent guessing.

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%, so baseline is 3. The description adds no extra meaning beyond the schema; it does not clarify 'enterprise' path meaning, nor pagination defaults or limits beyond schema hints.

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-level labels' clearly specifies the action (list) and resource (enterprise-level labels), distinguishing it from siblings like gitee_get_label (which likely targets a different scope) or gitee_create_label.

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 vs alternatives. For example, it doesn't contrast with project-level label listing tools like gitee_list_project_labels, nor does it mention prerequisites or context for enterprise labels.

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