webhooks_delete_instance

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

With no annotations, the description carries the full burden of behavioral disclosure, and it discloses nothing beyond the HTTP verb. It does not say the deletion is permanent/irreversible, what happens to existing deliveries or pings tied to the webhook, or whether special permissions are required. The raw method implies mutation but gives no consequence detail.

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 short but its only content is the method-plus-path repeated identically inside parentheses, meaning roughly half the text is pure duplication with zero informational value. It is not padded with prose, but it does not earn its own tokens.

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?

For a destructive single-resource delete with no annotations and no output schema, an agent needs at minimum to know the action is irreversible and tied to a valid webhook id. None of that is present, so the definition is inadequate for its complexity and safety profile.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents 'id'. The description adds no format, uniqueness, or sourcing detail beyond what the schema provides, which is the baseline for fully covered parameters.

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 states a verb (DELETE) and a resource path (/v1/webhooks/{id}), so the operation is identifiable. However it is essentially the tool name restated as a route, with the route duplicated verbatim in parentheses, and it offers no differentiation from the sibling marketplace_webhooks_delete_instance. This lands at 'vague purpose' rather than a clearly articulated intent.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or the surrounding webhook lifecycle (create/get/update). The operation is inferable from the name alone, but the description itself supplies nothing.

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