ghl_ad_fb_conversation_form_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating safe read-only behavior. The description adds endpoint and OAuth scope details, which are useful but do not significantly expand on behavioral traits beyond the annotations. No contradiction is present.

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 with a clear title and purpose statement. It includes endpoint and OAuth details, which may be extraneous for an AI agent but do not cause significant bloat. It is well-structured and 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?

The description lacks any information about the return value or output structure. Since no output schema is provided, the agent has no indication of what fields or data the list will contain. This is a notable gap for a list operation, but the annotations and existing details provide moderate context.

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?

Input schema coverage is 100%, and the description adds no additional meaning beyond the schema's parameter descriptions ('Is draft', 'Location identifier'). The agent can rely on the schema, but the description does not clarify how or when to use the optional isDraft parameter.

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 'get' and 'retrieve' and the resource 'Facebook conversation lead forms'. It distinguishes from sibling tools like ghl_ad_fb_lead_form_get and ghl_ad_fb_page_lead_form_list by specifying 'conversation forms', making the purpose specific and unambiguous.

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 is provided on when to use this tool versus related siblings such as ghl_ad_fb_lead_form_get or ghl_ad_fb_page_lead_form_list. There are no stated exclusions or context for when not to use this tool, leaving the agent to infer usage.

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