gitea_update_repository

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Update' implies mutation, the description fails to specify whether unspecified fields are preserved, if the operation is idempotent, what authorization is required, or what the response contains. It only minimally indicates which categories of settings can be modified.

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?

The description is a single sentence and generally efficient, but the '[UNIFIED]' prefix is metadata clutter that does not help the agent understand or select the tool. The core content is appropriately concise.

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?

Given the high complexity (14 parameters, 0% schema coverage, no annotations, no output schema), the description is inadequate. It provides a high-level summary but leaves critical gaps in parameter semantics, behavioral specifics, and return value documentation that an agent would need to invoke this tool correctly.

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?

With 0% schema description coverage, the description must compensate for 14 parameters (3 required, 11 optional). It mentions 'name, description, visibility, and features' which maps to roughly 4-5 optional parameters, but completely omits documentation for the required parameters (site, owner, repo) and several optional ones (website, archived, default_branch, merge settings). This is insufficient compensation for the schema gap.

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 clearly states the verb (Update) and resource (Gitea repository settings), and lists specific setting categories (name, description, visibility, features). However, it does not explicitly differentiate from sibling tools like gitea_create_repository or gitea_delete_repository, and the '[UNIFIED]' prefix adds noise without semantic value.

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 is provided on when to use this tool versus alternatives, prerequisites (e.g., required permissions), or whether partial updates are supported. The agent receives no instruction on authentication requirements or side effects.

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