gitea_create_repository

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions 'auto-initialization,' it fails to state that this is a destructive/write operation, does not describe error conditions (e.g., if the repository already exists), and does not disclose return values or idempotency characteristics.

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 brief at two sentences, but the '[UNIFIED]' tag at the beginning is structural noise that does not contribute to tool selection. The content is front-loaded with the core action, though the prefix reduces clarity.

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 complexity (10 parameters, no output schema, no annotations), the description is insufficient. It lacks explanation of the 'site' parameter (Gitea instance URL?), authentication context, error handling, and the interaction between optional parameters like 'gitignores' and 'auto_init'.

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?

With 0% schema description coverage across all 10 parameters, the description fails to compensate adequately. It implicitly references 'auto_init' via 'auto-initialization' and hints at the 'org' parameter by mentioning organization repositories, but provides no semantic context for critical parameters like 'site', 'private', 'license', 'gitignores', or 'default_branch'.

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 the verb (Create) and resource (Gitea repository), and distinguishes scope by mentioning support for both user and organization repositories. However, the '[UNIFIED]' prefix appears to be metadata leakage rather than descriptive content, and it does not explicitly differentiate from sibling tools like gitea_update_repository.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., gitea_update_repository for existing repos), nor does it mention prerequisites such as authentication requirements or whether the target organization must exist beforehand.

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