Gitea: Test webhook

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

Annotations declare destructiveHint=true and idempotentHint=false, yet the description frames this as a harmless verification. It does not explain why a test is destructive — e.g., that the payload fires real downstream consumers or creates visible events — nor does it cover permissions or repeat-call side effects. The annotations carry the safety profile, but the description could add useful context about the consequences of the test payload.

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 wasted clauses. The '[UNIFIED]' prefix is noise that adds no meaning for an agent, which keeps it from a 5.

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?

For a four-required-parameter, destructive-labeled mutation with no output schema, the description is too thin. It says nothing about what payload is sent, what is affected by the test, what the result looks like, or what permissions are needed.

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% and all four parameters (site, owner, repo, webhook_id) are required, but the description mentions none of them. It conveys only that a webhook is the target, leaving the meaning of site/owner/repo and the webhook identifier 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?

The description states a specific verb and resource: send a test payload to a webhook to verify it works. This is clearly distinguishable from gitea_create_webhook, gitea_delete_webhook, and gitea_update_webhook, but it never names those alternatives explicitly.

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 phrase 'to verify it's working' implies the diagnostic use case, but there is no explicit when-to-use vs. when-not guidance and no mention of the sibling tools that manage webhooks. The agent must infer the routing.

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