gitea_list_pull_requests

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

No annotations provided, and description carries minimal burden. While 'List' implies read-only, there's no disclosure of pagination behavior, filter logic (how multiple filters combine), rate limits, or whether results include closed PRs by default (the schema default is 'open' but this isn't explained).

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?

Brief (one sentence) but front-loaded with the non-functional '[UNIFIED]' tag. The phrase 'with filters' is too vague to earn its place given the lack of parameter documentation elsewhere.

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?

Grossly inadequate for a 9-parameter list operation with no output schema or annotations. Missing: pagination details (max limit), filter behavior, required authentication scope, and return value structure. The description does not meet the minimum needs for a tool of this complexity.

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?

With 0% schema description coverage across 9 parameters, the description must compensate significantly. It only mentions 'with filters' generically without explaining what filters exist (state, labels, milestone), their formats, or that 'site'/'owner'/'repo' form the required repository context. Fails to document pagination parameters.

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 the basic action (List) and resource (pull requests in a Gitea repository) but fails to distinguish from sibling 'gitea_get_pull_request' (single fetch vs. list) or clarify scope. The '[UNIFIED]' prefix is metadata noise that doesn't help selection.

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?

Provides no guidance on when to use this versus 'gitea_get_pull_request' or other PR-related tools. No mention of pagination strategy despite 'page' and 'limit' parameters, or how to handle large result sets.

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