ghl_ad_fb_page_lead_form_create

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

Annotations indicate non-readonly, non-idempotent, non-destructive. The description adds OAuth scopes, which is useful for authorization. However, it does not disclose side effects or state changes beyond the creation action itself. The description adds marginal value over 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 brief (two lines plus endpoint/scopes) but lacks structured usage guidance. It is concise but not optimally front-loaded for quick decision-making. Every line serves a purpose, but more context would improve usability.

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?

Given the complexity (nested objects, many properties, no output schema), the description does not explain the response format or mention that forms may need separate publishing steps. The agent lacks context about the full lifecycle.

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 detailed descriptions for all parameters and nested objects. The description does not add meaning beyond what the schema already provides. Achieves the baseline of 3 for high-coverage schemas.

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 it creates a lead gen form on a Facebook page, using a specific verb and resource. It distinguishes from sibling tools like ghl_ad_fb_page_lead_form_list and ghl_ad_fb_lead_form_get, which handle listing and retrieval.

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 guidance on when to use this tool versus alternatives such as ghl_ad_fb_conversation_form_create. It mentions OAuth scopes but lacks contextual prerequisites or exclusions. The agent is left to infer usage from the name alone.

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