Bulk Delete Triggers (Deprecated)

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

Beyond the annotations (destructiveHint=true), the description discloses that the operation permanently removes triggers, cannot be undone, and repeat calls return 404. It also details failure modes (401/403/404) and the deprecation timeline, providing significant behavioral context that the annotations alone do not offer.

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 serves a purpose: purpose, limits, deprecation guidance, prerequisite resolution, permanence warning, failure modes, required parameters, API reference, and endpoint. It is front-loaded with the core purpose and constraints, making it easy for an agent to scan.

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's destructive nature, single parameter, and no output schema, the description covers all essential context: prerequisites, limits, failure behavior, deprecation, and the exact endpoint. This is sufficient for an agent to select and invoke the tool correctly without additional lookups.

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?

With 100% schema coverage for the single hook_id parameter, the baseline is 3. The description adds value by requiring that hook_id identify an existing parent record and instructs the user to resolve it with the matching list tool first, plus it explicitly notes 'Required parameters: hook_id' for clarity.

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 starts with a specific verb and resource: 'Delete multiple webhook triggers in a single request.' It clearly states the scope constraints (same hook, company/project scope, max 500) and distinguishes itself from sibling bulk delete tools by emphasizing the single-request batch behavior and deprecation status.

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 explicit when-to-use guidance: all triggers must be within the same hook, scope must be company/project, and max 500. It gives actionable alternatives by directing the user to find a newer version via procore_search_endpoints, and it instructs to confirm the parent hook_id with a list tool before calling, which is crucial for correctness.

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