gitee_list_webhooks

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

No annotations are present, so the description must carry the full burden. It merely restates the name without disclosing traits like pagination behavior (page/per_page parameters), permission requirements, or response structure. The description adds minimal value beyond the tool name.

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 concise at 5 words, but it is too short to be effective. It front-loads the core purpose but omits necessary context. While there is no wasted text, the conciseness comes at the cost of completeness, resulting in a borderline acceptable score.

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 the tool's complexity (4 parameters, no output schema) and the presence of related siblings, the description is insufficient. It fails to mention pagination support or how to iterate through pages, which is critical for correct invocation. The description is incomplete for an agent relying solely on it.

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 100%, so the parameters are already well-documented in the schema. The description adds no extra meaning beyond the schema, such as clarifying that 'page' and 'per_page' control pagination or that 'owner' and 'repo' are required. Baseline score of 3 is appropriate.

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 'List webhooks for a repository', with a specific verb, resource, and scope. It distinguishes from sibling tools like gitee_get_webhook (single) and gitee_create_webhook (create), making its purpose unambiguous.

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 guidance is provided on when to use this tool versus alternatives. For example, it does not explain that this lists all webhooks (supporting pagination) while gitee_get_webhook retrieves a single one. The description lacks any contextual direction.

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