Gitea: Create release

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is largely covered. The description adds useful context beyond that: the operation creates a tag as well as release metadata, and draft releases are hidden until published. It does not disclose what happens on a duplicate tag, permission requirements, or whether prerelease affects visibility, leaving meaningful gaps for a mutation tool.

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?

Two short sentences with the core action front-loaded and no filler. It is efficiently written, though the brevity comes at the cost of the parameter and usage detail noted elsewhere.

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 at 0% schema coverage and no output schema, the description should carry most of the explanatory weight, but it covers only one parameter and no error or return behavior. An agent would have to guess at target_commitish semantics and prerelease effects to call this correctly.

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 0% across 9 parameters, so the description carries the full burden and only explains ``draft``. It says nothing about tag_name, target_commitish (which commit/branch the tag points to), prerelease, name vs body, or what site/owner/repo refer to. One of nine parameters is addressed, which is a substantial shortfall.

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 gives a specific verb and resource: 'Create a release (tag + release metadata) on a Gitea repository.' The parenthetical clarifies that a tag is created alongside the release metadata, which helps distinguish it from a plain tag-creation sibling. It stops short of explicitly naming which sibling to use instead, but the core purpose is unambiguous.

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 only guidance is the inline note that setting ``draft`` hides the release from users until published, which is parameter behavior rather than when-to-use advice. Nothing tells the agent when to choose this over gitea_create_tag or how it relates to gitea_upload_release_asset. No prerequisites (e.g. permissions, whether the tag must already exist) are stated.

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