Gitea: Fork repository

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

Annotations already declare readOnlyHint=false, destructiveHint=false-style safety profile is absent here (it sets destructiveHint=true and idempotentHint=false), so the bar is lower; the description still adds two non-obvious behavioral facts: the fork's default destination account and the fact that ``name`` renames the resulting fork. It does not address what happens if a fork already exists (relevant given idempotentHint=false) or any permission requirements, which keeps it from a 5.

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?

Two short sentences, front-loaded with the operation and followed by the two behavioral qualifiers. No preamble, no restatement of the title, nothing that could be cut.

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 five-parameter mutation with no output schema and no parameter descriptions, the definition leaves gaps: the identity of the source (site/owner/repo), the response shape, and the existing-fork case are all unaddressed. It is adequate to invoke the tool on the happy path but not complete for a non-idempotent, non-read-only operation.

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%, so the description must compensate, and it only does so for two of five parameters (``organization`` default and ``name`` rename semantics). ``site``, ``owner`` and ``repo`` are left entirely to the schema, which provides no descriptions at all, so meaning is only partly filled in.

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?

"Fork a Gitea repository" is a specific verb+resource that cannot be confused with create_repository, update_repository or get_repository in the sibling list. The target server/owner/repo framing is implicit in the verb, but the description never explicitly contrasts forking with creating a new repo, so it stops short of a 5.

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?

It gives one conditional routing rule (omit ``organization`` to fork under the calling user), which is really a default-behavior statement rather than when-to-use guidance. It never states prerequisites such as needing read access to the source repo, nor when an agent should prefer create_repository over forking; usage is implied rather than spelled out.

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