ghl_conversation_ai_delete_action

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

Description discloses that deletion is permanent and cannot be undone, and provides OAuth scope (conversation-ai.write) and endpoint details. This adds significant value beyond annotations which only indicate destructiveness.

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?

Concise and front-loaded with the action statement. Includes necessary technical details without verbosity, though endpoint info could be considered extra.

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 tool with no output schema, the description covers purpose, irreversibility, required permissions, and resource identification. Lacks mention of prerequisites or response behavior.

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?

No parameter descriptions in the description text. Schema coverage is only 50% (actionId described), but the description adds no insight into agentId or any parameter semantics.

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 states 'Permanently deletes an action' with a specific verb and resource. It distinguishes from sibling tools like ghl_conversation_ai_delete_agent by targeting 'action' specifically.

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 this tool versus alternatives like update_action or create_action. The warning about irreversibility provides caution but no comparative usage context.

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