gitee_create_enterprise_repo

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

The description only says 'create', which implies a mutation, but does not disclose permissions, side effects, or return behavior. Without annotations, the description fails to provide necessary behavioral context.

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 no wasted words, front-loading the verb and resource. It is appropriately concise for a simple creation action, though it could benefit from additional 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?

With 9 parameters, 2 required, and no output schema, the description is insufficient. It does not explain the enterprise scope, required permissions, or what the tool returns, leaving the agent underinformed.

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 each parameter having a brief description. The tool's description does not add meaning beyond the schema, but the schema itself provides adequate parameter semantics. Baseline 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 'Create a repository in an enterprise', specifying the verb (create) and the resource (repository in an enterprise). This distinguishes it from sibling tools like gitee_create_org_repo (for organizations) and gitee_create_user_repo (for personal accounts).

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 such as gitee_create_org_repo or gitee_create_user_repo. There is no mention of prerequisites or context for enterprise repository creation.

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