gitea_list_pr_reviews

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The word 'all' implies comprehensive listing without filtering, but the description omits pagination behavior, authentication requirements, rate limits, and what review states are included (e.g., dismissed reviews).

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 description is brief (one sentence), but the '[UNIFIED]' prefix is noise that doesn't help the agent. Otherwise efficiently structured without unnecessary verbosity.

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 tool with 4 required parameters and no output schema or annotations, the single-sentence description is inadequate. It fails to document parameter purposes, return structure, or error conditions necessary for confident invocation.

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% (no parameter descriptions), and the description text fails to compensate by explaining any of the four parameters (site, owner, repo, pr_number). The description adds zero semantic value beyond the parameter names themselves.

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 verb 'List' and resource 'reviews on a pull request', identifying the tool's core function. However, the '[UNIFIED]' prefix is extraneous metadata that doesn't aid clarity, and the description doesn't explicitly distinguish 'reviews' from sibling tool 'gitea_list_pr_comments' or differentiate from 'gitea_get_pull_request'.

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 provided on when to use this tool versus alternatives like gitea_list_pr_comments or gitea_get_pull_request. No mention of prerequisites (e.g., PR must exist) or common usage patterns.

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