sendook_delete_webhook

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

Adds context beyond annotations: 'stops all event deliveries'. Annotations already indicate destructiveHint=true, but description reinforces the irreversible effect and mentions return value.

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?

Two sentences plus functional argument/return description. No wasted words; front-loads the action.

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?

Adequate for a delete operation: explains what happens, required parameter, and return type. Missing error handling or permission context, but annotations fill some gaps.

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?

Description repeats what is in the schema ('webhook_id: Webhook to delete') without adding format, constraints, or validation rules. Schema coverage is 0%? Actually the schema has a description for webhook_id, so the description adds minimal value.

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?

Clearly states 'Delete a webhook subscription' and describes the effect ('Removes the webhook and stops all event deliveries to its endpoint'), distinguishing it from create, get, list, test, and other sibling tools.

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?

No explicit guidance on when to use or not use this tool versus alternatives. The purpose is implied but lacks context like prerequisites or side-effect warnings.

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