ghl_ad_li_account_delete

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

Annotations provide destructiveHint=true, readOnlyHint=false, and idempotentHint=true, which are consistent with description. The description adds technical details (endpoint, OAuth scopes) but does not disclose deeper behavioral traits like whether the deletion is reversible, what side effects occur, or response behavior. 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?

The description is relatively concise but includes some redundant phrasing ('Delete ad account' appears in both title and description). It includes endpoint and OAuth info, which adds value but could be more tightly structured.

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?

The tool is simple with two required parameters and no output schema. The description provides enough context for basic understanding but lacks information about the return value (e.g., success confirmation). It does not explain what happens after deletion or if any cleanup occurs.

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% with descriptions for both parameters (locationId, adAccountId). The tool description does not add any additional parameter meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 ad account' / 'Remove a LinkedIn ad account connection from a location') and the resource (LinkedIn ad account connection). It distinguishes from sibling tools that operate on different platforms (e.g., ghl_ad_fb_account_delete, ghl_ad_google_account_delete) and from read/list tools (ghl_ad_li_account_get, ghl_ad_li_account_list).

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 implies usage for removing a LinkedIn ad account connection from a location, but does not explicitly state when to use this tool versus alternatives (e.g., other platform delete tools) or provide prerequisites, exclusions, or when not to use it.

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