list_webhooks

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

The description is minimal and does not disclose behavioral details such as pagination, authentication requirements, or the structure of the returned list. Since no annotations are provided, the description carries the full burden, which it fails to fulfill beyond the basic action.

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 a single sentence with no redundant words. It is front-loaded and efficiently conveys the core purpose, with zero waste.

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, pagination options, no output schema), the one-line description is insufficient. It does not explain what the response looks like, nor the effect of pagination parameters, making it incomplete for an agent to use the tool 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?

The input schema covers owner and repo with descriptions, but page and per_page parameters lack descriptions. The tool description does not mention these pagination parameters or add any meaning beyond what the schema already provides, leaving the undocumented parameters unexplained.

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 that the tool lists webhooks for a repository, using the specific verb 'Lista' (lists) and the resource 'webhooks de un repositorio' (webhooks of a repository). This distinguishes it from sibling tools like get_webhook or create_webhook, which imply singular retrieval or creation.

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 description provides no guidance on when to use this tool versus alternatives such as get_webhook for a single webhook or create_webhook for creating one. It is a bare statement of functionality with no usage context or exclusions.

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