ghl_ad_fb_integration_create

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

Annotations indicate readOnlyHint=false and destructiveHint=false, meaning the tool modifies state but is not destructive. The description adds 'Create' which aligns, but does not disclose additional traits such as whether existing integrations are overwritten, rate limits, authentication scopes beyond OAuth scopes listed, or potential side effects. The description leans entirely on annotations for safety profile.

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 three sentences with no fluff. The first sentence repeats the title (minor redundancy), but the second and third add meaningful context about purpose and endpoint/OAuth scopes. It is efficiently structured and front-loaded with the core action.

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 has no output schema, and the description does not specify return values (e.g., integration ID, success message). Given the complexity of creating an integration, an agent would benefit from knowing what to expect as a result. The description is incomplete for a mutation tool without output schema.

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 input schema has 100% description coverage for all parameters (pageId, locationId, adAccountId). The description adds context like 'for a location with page and ad account', which groups the parameters semantically. However, it does not provide further details beyond what the schema already offers. Baseline 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 title and description clearly state 'Create Facebook integration' with additional detail about creating an ad integration for a location. The verb 'create' and resource 'Facebook ad integration' are specific, and the tool is well-distinguished from sibling tools like `ghl_ad_fb_integration_get` and `ghl_ad_fb_integration_delete`.

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 the tool is used to create an integration for a location with page and ad account, but it does not explicitly state when to use it versus alternatives like getting or deleting integrations. No prerequisites, ordering, or conditions are mentioned, leaving the agent to infer usage context.

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