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

The description explicitly states that a webhook subscription is deleted, which clarifies the target of destruction. However, it adds no behavioral context beyond what annotations already provide (destructiveHint, idempotentHint). It does not mention side effects, reversibility, or response behavior.

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 a single, concise sentence that is front-loaded and contains no unnecessary information. It effectively communicates the essential purpose and key parameter.

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 simple delete operation with one parameter and no output schema, the description is largely complete. It covers the action and target, while annotations handle safety traits like destructive and idempotent hints. It doesn't mention return values or post-delete state, but these are not critical for such a tool.

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?

The schema has one required 'id' parameter with no description. The description says 'by id', which clarifies that the parameter identifies the webhook subscription to delete. This adds minimal meaning beyond the schema, but does not provide details about id format or source.

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 uses a specific verb ('Delete') and resource ('webhook subscription') and specifies the key identifier ('by id'). This clearly differentiates it from sibling tools like relm_create_webhook or relm_get_webhook. The purpose is unambiguous.

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 no guidance on when to use this tool versus alternatives like relm_manage_webhook. It simply states the action without context, prerequisites, or exclusions. The usage context must be inferred entirely from the tool name.

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