List Company Webhooks Deliveries

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds value by describing pagination behavior (page/per_page, pagination metadata), the returned JSON array, and required parameters. No contradiction with annotations.

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?

Five sentences front-loading purpose and usage. Includes endpoint info which may be helpful for context. Could be slightly more concise but overall well-structured and no unnecessary fluff.

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 9 parameters and no output schema, the description covers purpose, pagination, filtering, required params, and return type ('paginated JSON array of Webhooks'). It mentions pagination metadata. May lack specific delivery object structure, but without output schema, this is adequate for an agent to understand the tool's output.

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 detailed descriptions for all parameters. The description adds marginal value by explaining page/per_page control pagination and response includes metadata. For filter parameters, schema already covers semantics. Baseline 3 is appropriate as description does not significantly enhance beyond schema.

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 it returns an array of webhooks deliveries for the company. It explicitly says 'for the company' distinguishing it from sibling tools like list_project_webhooks_deliveries. It also enumerates use cases: paginated overview, finding IDs, filtering.

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 clear when-to-use guidance: 'when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not mention when not to use or alternatives (e.g., list_project_webhooks_deliveries), but the context from the name and sibling list should suffice. Nearly comprehensive.

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