Gitea: Request pr reviewers

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=true, so the write/repeat behavior is covered. The description adds nothing beyond that: it doesn't say whether existing reviewers are replaced, whether reviewers are notified, what permissions are needed, or what identifiers the reviewers must be. Not contradictory, just empty.

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 is well front-loaded, but it is under-specified rather than concise in the productive sense, and the bracketed '[UNIFIED]' marker consumes space without informing the caller.

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 five-required-parameter mutation with no output schema and no parameter documentation anywhere, one sentence is far too thin. An agent can identify the action but not how to construct a correct call or what effect it has on the PR's reviewer set.

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 five parameters are required with 0% schema description coverage, and the description supplies no meaning for any of them. It does not clarify that reviewers is an array of usernames (versus team names or IDs), nor the format of site/owner/repo/pr_number, so the agent must guess.

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 names a specific verb and resource ('Request reviewers for a pull request'), so an agent can tell it apart from review-submission or listing tools by action alone. The '[UNIFIED]' prefix is an unexplained tag that adds no discriminating information.

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 use this instead of siblings such as gitea_create_pr_review (submit an actual review) or gitea_get_pull_request. No preconditions, no exclusions, no alternatives are named.

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