list_org_webhooks

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

The description says 'List all webhooks' which implies a complete list, but the schema includes page and per_page parameters, indicating pagination. This is not disclosed in the description, creating a potential misunderstanding about behavior. No annotations exist to fill this gap.

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, direct sentence that front-loads the verb and resource. No fluff, and it immediately conveys the tool's purpose. Efficient and appropriately sized.

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 annotations, no output schema, and a description that omits pagination behavior and return format, the tool is under-specified. Given the presence of sibling tools, a short note about org vs repo scope or pagination would improve completeness.

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 coverage is 100% with parameter descriptions already provided. The description adds no extra meaning to the parameters (e.g., what 'all' means in the context of pagination). Baseline 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 the action ('List') and resource ('webhooks') scoped to 'an organization'. It distinguishes itself from sibling tools like 'list_repo_webhooks' and create/update/delete operations, leaving no ambiguity about its function.

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?

Usage is implied by the name and description — it's the org-level listing counterpart to list_repo_webhooks. However, it does not explicitly mention when to use it vs alternatives or provide any exclusion criteria, so it falls short of clear guidance.

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