Gitea: Upload status

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, and "Query" is consistent with that, so no contradiction. Beyond the annotation, the description adds that the response includes target metadata, which is genuinely useful. It does not disclose what status values can come back, whether a session can be expired or unknown, or whether polling is rate-limited.

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 padding or redundancy. The only wasted token is the "[UNIFIED]" prefix, which conveys nothing to an agent selecting the tool.

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 two required, undocumented parameters and no output schema, the definition needs to explain the site/session_id roles and roughly what a status result looks like. It does neither, so an agent knows the intent but not how to fill the arguments or interpret the reply.

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 carry the burden for both parameters, and it does not. "session_id" is only obliquely referenced by the word "session," and "site" is not mentioned at all, leaving the agent to guess that it selects the Gitea instance.

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: query the status of a Gitea binary upload session, plus target metadata. That distinguishes it from siblings such as gitea_upload_chunk, gitea_upload_finish, and gitea_upload_abort. The bracketed "[UNIFIED]" prefix adds no meaning but does not obscure the core purpose.

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?

The description says what the tool does but never says when to call it: no indication that it is used between chunk uploads to poll progress, or to recover state after a dropped session. No alternatives are named, even though gitea_upload_chunk, gitea_upload_finish, and gitea_upload_abort sit adjacent and an agent must choose among them.

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