Gitea: List webhooks

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

Annotations already declare readOnlyHint=true, so the safety profile is covered structurally; the description's contribution is limited to confirming the repository scope. It says nothing about pagination, result caps, ordering, or what happens if the caller lacks webhook visibility permission — meaningful gaps for an admin-adjacent listing endpoint.

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 short sentence with the scope statement front-loaded; nothing is padded or buried. The '[UNIFIED]' tag is the only wasted token.

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, the description should indicate what a returned webhook looks like (id, type, URL, events, active flag) and whether the list is paginated. With three fully undocumented required parameters and no such return-value context, the definition leaves too much for the agent to guess.

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% for all three required parameters (site, owner, repo), so the description carries the full burden and discharges none of it. It never explains that 'site' is the Gitea instance/host, nor gives owner/repo format expectations (slug vs display name, owner type).

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+resource: lists webhooks, scoped to a repository. That is unambiguous and distinct from the other list_* siblings (branches, labels, releases, etc.). The only weakness is the meaningless '[UNIFIED]' prefix, which adds no clarifying information.

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 choose this tool, no mention of prerequisites such as needing repo admin/owner permissions to read webhooks, and no note that only repository-level webhooks are covered (org/global webhooks excluded). The agent must infer all of this.

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