List Project Webhooks Hooks

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds that the tool returns a paginated JSON array with pagination metadata, uses page/per_page, and lists required parameters. No contradictions.

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 relatively concise with a few sentences, front-loaded with the main action and purpose. It includes implementation details (API version, endpoint) but no wasted sentences.

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 is a simple list operation with good annotations and full schema coverage, the description is sufficient. It covers pagination, filtering, and return format without needing an output schema.

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 baseline is 3. The description mentions required parameters (company_id, project_id) and pagination, but these are already in the schema. It does not add significant new meaning beyond the 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 for the project using a specific verb ('Returns'). It mentions enumeration for paginated overview, finding IDs, and filtering. It does not explicitly differentiate from sibling list tools like list_company_webhooks_hooks, but the scope 'for the project' is implied.

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 says 'Use this to enumerate Webhooks when you need a paginated overview, to find IDs, or to filter by query parameters.' This provides clear usage context but lacks when-not to use or explicit alternatives among siblings.

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