webhooks.delete

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

With no annotations provided, the description carries the full burden of disclosure but only states that deletion occurs. It fails to specify if the deletion is permanent, immediate, idempotent, or if it affects in-flight webhook deliveries. It implies mutability but lacks critical behavioral context.

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 single sentence is front-loaded with the verb, contains no redundancy, and efficiently communicates the core operation. Its brevity is appropriate in principle, though the lack of supporting detail creates gaps elsewhere.

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 zero schema descriptions and no annotations, the description is insufficient for a destructive operation. It omits critical details about the required identifier, confirmation behavior, and side effects, leaving the agent underspecified despite the tool's simple signature.

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 0% (the 'id' parameter is undocumented in the schema), yet the description fails to compensate by explaining what the 'id' parameter represents (e.g., 'the webhook endpoint ID to delete'). It adds no parameter semantics 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?

States a specific verb ('Delete') and resource ('Ryft webhook endpoint'), providing clear scope. However, it does not explicitly differentiate from sibling tools like 'webhooks.update' (which might disable rather than delete), so it lacks explicit sibling differentiation.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., when to delete vs. update a webhook) or any prerequisites. The agent is given no criteria to select this tool aside from the generic intent to delete.

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