gitea_action

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

With no annotations, the description carries the full behavioral burden, and it does disclose useful operational traits: every create_test_run dispatch gets a unique request_id suffix so concurrent runs never collide, and get_test_results returns status, conclusion, and the last 80 log lines. However, for a tool that merges PRs, deletes mirrors, and writes files, it says nothing about auth requirements, permission scopes, whether destructive actions are reversible, or rate limits.

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 second paragraph is tight and front-loads the test workflow with a clear purpose. The first paragraph is a long, comma-chained enumeration that substantially duplicates the action enum's own description, so a meaningful share of the text is redundant rather than additive.

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 a 52-parameter dispatcher with no output schema and no annotations, the description covers the highest-friction flow (test dispatch/polling) well and states the overall scope. It leaves gaps an agent would care about: which parameters pair with which actions outside the test path, return shapes for read operations, and the consequences of the mutating actions (merge, close, delete_push_mirror). The rich schema compensates partially, but not fully.

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 coverage is 100%, so the baseline is 3, but the description adds cross-parameter guidance the schema cannot: it shows the create_test_run(owner, repo, ref, files) call shape and the get_test_results(owner, repo, run_id) counterpart, and explains the run_id vs request_id substitution. This ties otherwise-scattered parameters into a usable workflow, though it does not clarify parameter applicability for the remaining actions.

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 opens with a specific verb and resource ('Interact with the self-hosted Gitea forge REST API') and enumerates the concrete capability groups (repos, branches, files, commits, Forge Actions runs/jobs/logs, branches/commits, PRs, issues, push mirrors). The 'self-hosted Gitea' qualifier distinguishes it from sibling GitHub/GitLab/Bitbucket tools, so an agent can tell what this tool addresses without opening the 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?

It gives explicit when-to-use guidance for one sub-flow: create_test_run plus get_test_results is for running a few test files without waiting on full CI, and it explains passing request_id when a run is not yet visible. It also justifies push mirrors as the mechanism for downstream sync. But it offers no when/when-not guidance or alternatives for the 30+ other actions, leaving most selection to the schema.

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