gitea_create_pr_review

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

With no annotations provided, the description carries the full burden. It discloses the mutation nature (create) and the possible review states, but lacks details on side effects (notifications sent), authentication requirements, idempotency, or error conditions like attempting to review a closed PR.

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?

Extremely efficient single-sentence structure with action, resource, and enumerated options front-loaded. Despite the '[UNIFIED]' tag, there is zero wasted verbiage and every component earns its place.

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 6-parameter mutation tool with no output schema and zero annotations, the description provides the minimum viable context for the operation type and event values, but lacks completeness regarding return values, error handling, or coordinate parameter semantics.

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%, requiring heavy compensation. The description provides critical semantic values for the 'event' parameter (approve, request changes, comment) and implies the 'body' parameter purpose, but leaves four parameters (site, owner, repo, pr_number) without any semantic guidance beyond their names.

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 clearly states the specific action ('Create a review'), identifies the resource ('pull request'), and distinguishes this tool from siblings by specifying the three review event types (approve, request changes, or comment), which differentiates it from gitea_create_pr_comment.

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?

The parenthetical '(approve, request changes, or comment)' provides implied usage context for the event parameter, but there is no explicit guidance on when to use this tool versus gitea_create_pr_comment or prerequisites like the PR existing.

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