ghl_ad_fb_audience_delete

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

The description provides the endpoint URL and OAuth scopes, adding context beyond the annotations (destructiveHint, idempotentHint). It clearly indicates the destructive nature and that it's idempotent, but does not detail side effects beyond deletion.

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 concise and front-loaded with the core action, followed by endpoint and auth details. No redundant information; every sentence adds value.

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 description covers what the tool does, the endpoint, and auth scopes, but lacks error conditions, prerequisites (e.g., need for Facebook integration), or return values. Adequate for a simple delete operation but not fully comprehensive.

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%, so baseline is 3. The description does not add additional parameter semantics beyond what is already in the schema fields.

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 'Delete a Facebook custom audience by ID', specifying the verb (delete) and resource (Facebook custom audience). It distinguishes itself from sibling tools like ghl_ad_fb_audience_get and ghl_ad_fb_audience_list by focusing on deletion.

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 such as other delete tools or non-delete audience operations. It does not mention prerequisites or typical use cases.

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