get_webhook_collection

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description's only addition is the pagination hint; it says nothing about result ordering, project scoping, or response shape.

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?

Three sentences that restate the same idea ('Get all webhooks. Retrieve all webhooks.'), which is redundancy rather than front-loaded information. The pagination note is the only non-duplicated content.

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 list tool with a required nested query object, 0% schema coverage and no output schema, the description omits the required project scoping and pagination mechanics. An agent could not reliably invoke it from this text alone.

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 reported at 0% and the parameters are nested (page, limit, project_id). The description only gestures at pagination and never mentions that project_id is required, so it fails to compensate for the schema gap.

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?

States a clear verb+resource (get all webhooks), and 'all' hints at the collection scope, but it never distinguishes itself from the sibling get_webhook. The purpose is understandable yet vague on scope relative to the rest of the API.

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?

Only a weak hint that pagination should be used to 'find the webhooks you need.' There is no statement of when to use this instead of get_webhook, no prerequisites, and no exclusions.

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