Gitea: Close pull request

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the mutation profile is covered. The description contributes the semantic clarification that the change is a close rather than a merge, which matters, but omits what happens on an already-closed PR (relevant given idempotentHint=false), whether the branch is deleted, and any auth/rate-limit 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?

A single short sentence with the action front-loaded and zero filler; the scoping qualifier follows immediately. The only blemish is the unexplained "[UNIFIED]" token, which consumes attention without adding meaning.

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 four-parameter mutation with no output schema and no documented parameters, one sentence is thin. An agent gets the action but not the preconditions, side effects (e.g., whether linked branches or statuses change), or post-conditions needed to call it confidently.

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% and the description mentions no parameters at all. The names site, owner, repo and pr_number are fairly self-explanatory, but nothing clarifies the expected format of site (hostname vs full URL) or whether pr_number is repo-scoped, so the description does not compensate for the coverage gap.

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 and resource ("Close a pull request") and adds the qualifier "without merging", which cleanly separates it from gitea_merge_pull_request and implies the counterpart to gitea_reopen_pull_request. The only noise is the cryptic "[UNIFIED]" prefix, which conveys nothing to an agent.

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?

There is no explicit when-to-use guidance, no prerequisite conditions (does the caller need write permission? must the PR be open?), and no named alternative for related intents such as merging or reopening. The phrase "without merging" is the only implicit routing hint.

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