ghl_conversation_ai_delete_agent

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

Annotations already mark destructiveHint=true. The description adds value by clarifying permanence and scope (configurations and conversation history removed). OAuth scopes are also provided. No contradiction with annotations.

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?

Description is extremely concise and front-loaded. Title is repeated briefly, then key consequences, endpoint, and scopes. No superfluous sentences.

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 one-parameter delete tool with annotations providing destructive hint, the description covers permanence, scope, and auth requirements. It does not mention error cases or response format, but output schema is absent and annotations already indicate safe usage. Slightly more detail on prerequisites could elevate it.

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% (single parameter with description and example). The description does not add further meaning or context beyond what the schema provides. Baseline score of 3 applies.

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 the action (Delete Agent) and resource (AI agent), and explicitly mentions permanence and removal of configurations/history. This distinguishes it from sibling tools like update or get.

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 explicitly warns that the action cannot be undone and removes all associated data, helping the agent decide when to use it. However, it does not explicitly state when not to use it or suggest alternatives like update.

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