Gitea: Upload release asset

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the mutating/unsafe profile is carried by structured data. The description adds the useful behavioral constraint that content must be base64-encoded and small, but it does not explain what destructiveHint means here (e.g. whether an existing same-named asset is replaced) or what permissions/response to expect.

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 tight sentences with the primary use case front-loaded and the alternative routing second. The '[UNIFIED]' prefix is noise that adds no meaning, but otherwise there is no wasted wording.

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?

With no output schema, six fully undocumented required parameters, and a destructive mutation, the description does far too little: return value, size ceiling, overwrite behavior, and identifier formats all remain unknown. It is adequate for choosing the tool but thin for invoking it 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?

Schema description coverage is 0% across six required parameters, so the schema provides no semantics at all. The description only implicitly clarifies content_b64 (base64-encoded) and release_id (target release); site, owner, repo and filename formats (e.g. path-like names, site alias conventions) are left entirely undocumented.

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?

States a specific verb and resource (upload a base64-encoded release asset to a Gitea release) and immediately scopes it with the qualifier 'small', which is what separates it from the chunked/streamed siblings. An agent can distinguish this from gitea_upload_start/gitea_upload_finish without opening any schema.

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?

Gives an explicit routing rule: use this for small assets, use gitea_upload_start plus the returned HTTP upload URL and then gitea_upload_finish for larger files. The only gap is that 'small' has no numeric threshold, so the agent has to guess where the boundary lies.

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