gitea_list_user_repos

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

Discloses the 'public' filtering behavior which is critical context missing from annotations. However, fails to mention pagination behavior (despite page/limit params), rate limits, or error responses. With no annotations, description carries full burden and provides minimal safety/operational context.

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?

Single sentence, efficient length. Front-loaded with action verb. Minor deduction for '[UNIFIED]' metadata tag which consumes space without adding functional value for the agent.

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?

Missing output schema documentation (no output schema provided). With 4 parameters at 0% coverage and no annotations, the description is insufficiently complete. Should describe parameter semantics and return structure.

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 has 0% description coverage. Description implies 'username' via 'Gitea user' mention but fails to explain 'site' (URL? instance name?), 'page', or 'limit' parameters. Insufficient compensation for completely undocumented schema.

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?

Clear verb (List) and resource (public repositories of a Gitea user). Specifies 'public' scope and 'user' target, which helps distinguish from sibling gitea_list_org_repos. However, lacks explicit contrast with gitea_list_repos (likely authenticated/general listing).

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 on when to use versus gitea_list_repos or gitea_get_user. No mention of authentication requirements even though 'public' implies no auth needed. No prerequisites or error conditions described.

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