ghl_ad_fb_conversation_form_create

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

Annotations indicate non-readonly, non-destructive, and open world. The description adds endpoint details and required OAuth scope (adPublishing.write), which are behavioral constraints not covered by annotations. No contradictions.

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 extremely concise, with two key sentences plus endpoint and OAuth info. No superfluous text. Information is front-loaded.

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?

While the description covers endpoint and OAuth, it lacks details on response format, error handling, or prerequisites (e.g., existing Facebook integration). No output schema exists, so more context would be beneficial. Adequate but not complete.

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 the schema already documents all required fields. The description adds no extra semantic meaning beyond the schema; it merely repeats the schema verbatim. 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 description clearly states the verb 'Create' and the resource 'Facebook conversation lead form'. It distinguishes from siblings like ghl_ad_fb_conversation_form_list (list) and ghl_ad_fb_lead_form_get (get lead form) by specifying the action and resource type.

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 provides endpoint and OAuth scopes but does not explicitly state when to use this tool versus alternatives (e.g., when not to use it, prerequisites). Usage context is implied but not clearly delineated.

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