Gitea: Close issue

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds nothing on top: it does not say whether the close is reversible, how to undo it, whether permissions are needed, or whether closing a closed issue errors out.

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 short sentence is front-loaded and free of padding, so there is no wasted wording. However, its brevity comes from under-specification rather than economy — the space saved is space that should have carried behavioral and parameter detail.

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 mutation with four undocumented required parameters and no output schema, the description should explain the state change, reversibility, and parameter meanings. The annotations cover only the safety hint, leaving a substantial gap for an agent that must invoke 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?

There are four required parameters (site, owner, repo, issue_number) at 0% schema description coverage, and the description explains none of them. It does not clarify that issue_number refers to the issue's numeric index rather than its id, nor what 'site' means in a multi-instance Gitea context.

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?

"Close an issue" essentially restates the tool name gitea_close_issue and the title "Gitea: Close issue" without adding scope, state transition, or any distinguishing detail. The "[UNIFIED]" prefix is unexplained jargon that conveys nothing about behavior. An agent learns nothing beyond what the name already implies.

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 such as gitea_update_issue (which can set state) or gitea_reopen_issue. There is no mention of prerequisites like required permissions, issue state requirements (must be open), or what happens when closing an already-closed issue.

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