keap_delete_hook

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

With no annotations, the description must convey behavioral traits. 'Delete a REST hook' implies a destructive operation, but it doesn't disclose whether deletion is irreversible, if it requires specific permissions, or what side-effects occur (e.g., cancelling pending events). Minimal transparency.

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?

A single, clear sentence. Conciseness is high, though a bit more context (e.g., 'irreversibly removes a webhook endpoint') could be added without sacrificing conciseness.

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 the tool's simplicity (1 param, no output schema), the description is still incomplete. It lacks details on what happens after deletion, any return value, error handling, or prerequisites. The sibling tools list includes related hooks (create, update, verify) but no cross-reference.

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 100% (hook_key described in schema). The tool description adds no extra meaning beyond the parameter's own description ('Hook key to delete'). Baseline 3 for high coverage, but no added 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?

The description 'Delete a REST hook' clearly states the verb (delete) and the resource (REST hook). However, it does not differentiate from other delete tools (e.g., keap_delete_appointment) or provide additional context about what a REST hook is.

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 guidance is provided on when to use this tool vs alternatives. For instance, it doesn't mention that one might list or verify hooks before deletion, or any prerequisites. The description is purely operational.

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