gitee_list_enterprise_pulls

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only repeats the tool's name, offering no insight into side effects (none expected), pagination behavior, authentication needs, or that it returns a list. A minimal 'list' tool still benefits from stating read-only nature.

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 sentence with 4 words, no filler. It is maximally concise. While it could be longer, it does not waste words.

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?

For a tool with 8 parameters, no output schema, and no annotations, the description is insufficient. It lacks context about what constitutes an enterprise pull request, expected behavior (e.g., returns list), and how it fits with other enterprise list tools. The agent would need to infer too much.

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 8 parameters have descriptions in the schema (100% coverage). The description does not add any further meaning beyond what the schema already provides. For example, it could explain the relationship between 'enterprise' and 'state', but it does not. 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 clearly states 'List enterprise pull requests', indicating a specific verb and resource. However, it does not differentiate from similar sibling tools like gitee_list_enterprise_issue_pulls, which also lists pull requests in an enterprise context. The distinction is implicit but not explicit.

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. There is no mention of context, when-not-to-use, or how it compares to similar list tools like gitee_list_pulls or gitee_list_enterprise_issues. The agent receives no decision support.

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