Gitea: Create pr review

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

The annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this mutates state, but the description adds little beyond restating the action types. It does not explain that approving or requesting changes can affect mergeability, what permissions are needed, or whether a prior review is replaced.

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 definition is a single front-loaded sentence with no redundant clauses. It is efficient, though the unexplained '[UNIFIED]' token and the lack of any structural separation between purpose and action types slightly reduce 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?

This is a destructive mutation with six required-or-optional parameters, zero schema coverage, and no output schema. The description should at minimum explain the event values and body semantics, but it provides only a high-level action list, leaving the agent under-equipped to call it 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 six parameters, so the description carries the full burden. The parenthetical 'approve, request changes, or comment' hints at the event parameter's domain, but it never states the exact accepted values and leaves site, owner, repo, pr_number, and body entirely unexplained.

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 states a specific verb and resource ('Create a review for a pull request') and enumerates the three review actions, which distinguishes it from a plain PR comment tool. The unexplained '[UNIFIED]' prefix adds noise but does not obscure the core purpose.

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 guidance on when to choose this tool over siblings such as gitea_create_pr_comment or gitea_list_pr_reviews, and no prerequisites or conditions are described. The parenthetical action list implies what the tool is for but does not route the agent between alternatives.

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