delete_lead_sync_subscription

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

The description discloses the key behavioral effect of deletion—stopping webhook delivery—which is useful. But with no annotations, it omits other important behavioral details such as irreversibility, permission requirements, or side effects on other resources.

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 a single, front-loaded sentence that conveys action and consequence without any unnecessary words. It is clear and efficient.

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 destructive delete operation with no annotations and no output schema, the description is minimal. It does not explain how to obtain subscription_id, the role of ad_account_id, or any caveats around deletion, leaving the agent to infer important context.

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?

The schema documents subscription_id but leaves ad_account_id without any description. The tool description adds no meaning for either parameter, so the agent gets no help understanding ad_account_id's purpose or whether it is needed for the operation.

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 uses a specific verb 'Delete' and a specific resource 'lead-sync subscription', and clearly states the intended outcome ('to stop webhook delivery'). This strongly distinguishes it from sibling tools like create/list/get_lead_sync_subscription.

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 phrase 'to stop webhook delivery' implies the tool should be used when webhook delivery needs to be terminated. However, it does not explicitly address alternatives or provide conditions for when to choose this tool over related subscription operations.

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