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

The description states that the tool 'deletes' a webhook, which is an inherently destructive operation. Yet the annotation destructiveHint is false, directly contradicting the description's implied behavior. This mismatch could mislead an agent about side effects, and the description fails to add any mitigation (e.g., irreversibility warning).

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 two clean, front-loaded sentences with zero redundancy. It states the action first, then provides a practical pointer. Every word earns its place, making it an exemplary concise description.

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 deletion tool with no output schema, the description covers the essentials: what is deleted, the identifying parameter, and how to retrieve valid IDs. It does not mention irreversibility or ownership checks, but those are partially covered by the schema's walletAddress description. The misleading annotation increases the need for extra context, so a 4 is appropriate.

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?

Both parameters are already fully described in the schema (100% coverage), so the baseline is 3. The description adds value by pointing to list_webhooks as the source for webhookId, enriching that parameter's semantics. The walletAddress parameter is well-covered by the schema, so no further description is needed.

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 clearly names the action (Delete) and the resource (webhook registration by ID). It distinguishes this tool from siblings like register_webhook and list_webhooks by specifying the deletion operation. The phrase 'by ID' also hints at the key parameter.

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 gives explicit practical guidance: use list_webhooks to find webhook IDs, which establishes the prerequisite workflow. However, it does not discuss when not to use this tool or mention alternative deletion tools (e.g., delete_staking_policy). This is clear context but lacks exclusionary guidance.

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