gitea_list_repositories

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

Mentions that it returns a 'repository list with metadata', indicating read behavior. However, with no annotations provided, the description fails to disclose pagination behavior (despite having page/limit params), authentication requirements, or what 'UNIFIED' signifies about its behavioral differences from siblings.

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?

Appropriately concise with two sentences. The '[UNIFIED]' prefix is cryptic but the description is front-loaded with the core action. No wasted words, though the prefix could be explained or removed.

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?

Inadequate given the complexity: 5 parameters with zero schema coverage, no annotations, and no output schema. The description hints at 'unified' functionality but does not explain the pagination model, the metadata returned, or how it aggregates the sibling-specific list operations.

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 coverage is 0% with no descriptions, and the description completely fails to compensate. Critical parameters like `site` (likely an instance URL), `type` (likely filtering options), and `owner` are undocumented. The agent has no semantic guidance for any of the 5 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?

Clearly states the tool lists Gitea repositories and identifies the scope (user/organization/current user). However, it does not explicitly differentiate when to use this versus siblings like `gitea_list_user_repos` or `gitea_list_org_repos`, leaving some ambiguity about which tool to select.

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 explicit guidance on when to use this tool versus the more specific sibling list tools (`gitea_list_user_repos`, `gitea_list_org_repos`). The phrase 'for a user/organization or current user' describes capability but does not guide selection.

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