List Webhooks Deliveries (Deprecated)

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

Annotations already declare read-only and idempotent, but description adds details on pagination (page/per_page, pages remaining), error payloads with common HTTP statuses (401/403/404), and the read-only nature of the operation, aligning with annotations. No contradiction.

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 dense but every sentence carries unique information—deprecation, scope, usage, error handling, required params, endpoint. No redundancy or filler, and it front-loads the most critical deprecation and scoping details.

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?

The description covers deprecation timeline, alternative discovery, usage context, prerequisites, return type, pagination, read-only nature, failure modes, required parameters, and endpoint reference. Even without an output schema, it gives sufficient invocation information.

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%, so baseline is 3, but the description adds meaningful constraints: requiring company_id and/or project_id scope, and that hook_id must reference an existing parent record. It also clarifies that page/per_page control pagination beyond schema descriptions.

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 this tool lists webhooks deliveries within a company/project scope, and explicitly notes it is deprecated with a preferred alternative. It distinguishes itself by indicating it's for discovering deliveries or looking up an ID before calling another tool.

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?

Explicitly warns of deprecation and tells users to prefer a newer version via procore_search_endpoints. It also instructs to resolve hook_id first with a matching list tool, and describes when to use it. This gives clear when-to-use and when-not-to-use guidance.

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