Gitea: List user repos

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

The readOnlyHint annotation already establishes this is a safe read, so the description only needs to add context. It does contribute one meaningful behavior — results are limited to public repositories, so private repos will be absent — but says nothing about pagination defaults, authentication requirements, or result ordering/truncation.

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, front-loaded sentence with no filler. The '[UNIFIED]' prefix is a low-value tag that occupies the most salient position, which keeps it from a 5.

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 four-parameter tool with zero schema description coverage and no output schema, the definition is too thin: an agent cannot tell what 'site' expects, how paging works, or what fields the returned repository objects contain. The readOnly annotation covers safety, but the operational gaps remain substantial.

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% across four parameters, so the description must carry parameter meaning and it does not. Only 'username' is indirectly implied by 'of a Gitea user'; 'site' (which Gitea instance), 'page', and 'limit' are entirely unexplained in both schema and description.

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 states a specific verb (List), resource (repositories), and scope (public repos owned by a given Gitea user), which is enough to distinguish it from org-scoped or generic repository listings. It stops short of naming a sibling tool to route against, so it is clear but not maximally differentiating.

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 only usage signal is the word 'public' and the phrase 'of a Gitea user,' which imply the intended scenario but never state when to prefer this over listing org repos or listing repositories generically. There are no exclusions, prerequisites, or alternative-routing guidance.

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