x_api_delete_webhooks

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

With no annotations provided, the description carries the full transparency burden. It discloses the mutating high-risk nature, required bearer/OAuth tokens, environment-selection behavior, expected response shape, common failure conditions, and safety warnings about validating scope/payload/authorizationKey.

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 well-structured with labeled sections and front-loads the core purpose. The 'Use when: Delete webhook' line is redundant with the opening sentence, which adds slight clutter, but the overall organization is efficient and scannable.

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?

Despite lacking an output schema and annotations, the description covers purpose, permissions, environment behavior, parameter basics, expected response, failure conditions, recommended tools, and an example. This provides enough context for the agent to invoke the tool correctly in most situations.

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 0%, so the description must compensate. It explains webhook_id, scopeTenantId/scopeUserId/scopeAccountId selection for auth resolution, and credentialKey behavior. However, it does not clarify authorizationKey or preferredAuthType, leaving some parameter semantics to inference.

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 opens with the clear verb+resource statement 'Delete webhook.' It is unambiguous about the core action, but it does not explicitly differentiate from sibling tools like x_api_delete_webhooks_stream_link or x_api_validate_webhooks. The purpose is clear without being deeply scoped.

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 'Use when' and 'Do not use when' guidance, including alternatives: 'prefer x_schema_discovery or x_query_suggestion first' for exploration. It also lists recommended prerequisite and follow-up tools, giving the agent clear direction on when this tool is appropriate.

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