Gitea: Reopen issue

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: no note about permission requirements, whether reopening restores prior state or notifies watchers, or what happens when the issue is already open.

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 single sentence is front-loaded and free of padding, which is good. However, its brevity crosses into under-specification for a destructive mutation tool, and the "[UNIFIED]" tag is noise that consumes attention without informing.

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 destructive, non-idempotent mutation with four undocumented required parameters and no output schema, the description should at minimum explain parameter meaning and side effects. It provides only the bare action, leaving the agent to guess at identifiers and consequences.

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 four required parameters (site, owner, repo, issue_number) have 0% schema description coverage, so the description carries the full burden — and it mentions none of them. There is no indication of what "site" means (host/instance) or the expected format of owner/repo identifiers.

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?

States a specific verb+resource pair ("Reopen a closed issue"), which is immediately distinguishable from siblings like gitea_close_issue or gitea_reopen_pull_request. The opaque "[UNIFIED]" prefix adds no meaning, and no sibling is named explicitly, 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?

No guidance on when to use this versus alternatives, and no preconditions stated — notably that the issue must currently be closed for a reopen to make sense. The agent must infer everything about invocation context.

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