Gitea: Update repository

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, and the description adds essentially nothing beyond restating that settings change. It never explains the critical behavior for a 14-param patch tool: whether null/omitted fields leave existing values untouched, what happens when a repository is renamed, or whether archived/private require special permissions. With annotations carrying the safety profile, the remaining behavioral gaps still warrant a low score.

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 front-loaded sentence with no filler, and the leading "[UNIFIED]" marker signals a convention. It is efficient, though its brevity is partly under-specification rather than true concision for a tool this size.

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 destructive, non-idempotent mutation with 14 undocumented parameters and no output schema, one sentence is not enough. An agent cannot tell from the definition how to format boolean-like values or what a partial update will do to fields it omits, which risks incorrect or damaging calls.

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 14 parameters, so the description must compensate and it does not. It hints at four of them (name, description, private/visibility, has_wiki/has_issues/allow_* "features") but never explains the unusual string-typed booleans (private, archived, has_wiki as string|null rather than boolean), accepted truthy values, or the purpose of default_branch, website, and the three merge-strategy flags.

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 gives a specific verb and resource ("Update Gitea repository settings") and names example fields (name, description, visibility, features), so an agent knows exactly what object is being mutated. It does not distinguish itself from sibling tools such as gitea_create_repository or gitea_delete_repository, which keeps it from 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?

There is no guidance on when to use this versus create/delete/get, no prerequisites, and no statement of required permissions or scope. The only implied usage is the verb "update"; the agent must infer everything else.

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