gitea_list_webhooks

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

No annotations are provided, so the description must carry the full disclosure burden. It fails to mention that this is a read-only operation, what data structure is returned, or whether pagination applies. The '[UNIFIED]' prefix appears to be metadata noise without explanatory value.

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 description is appropriately brief at one sentence, but the '[UNIFIED]' prefix wastes space without adding functional clarity for tool selection. Otherwise efficiently structured.

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 zero schema descriptions, no annotations, and no output schema, this simple list tool requires more documentation than provided. The description lacks return value hints, parameter documentation, and behavioral constraints that would help an agent invoke 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%, requiring the description to compensate. While it mentions 'repository' implying the owner/repo parameters, it provides no explanation for the 'site' parameter or expected formats. Minimal semantic value added beyond the schema property names.

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 clearly states the specific verb 'List' and resource 'webhooks' with scope 'for a repository'. It distinguishes from sibling operations like create_webhook, delete_webhook, and get_webhook (singular) by explicitly stating 'List all'.

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?

No explicit guidance provided on when to use this versus gitea_get_webhook (which retrieves a single webhook), or prerequisites for repository access. The description states what it does but not when to prefer it over alternatives.

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