ad_manager_fb_get_conversation_forms

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond that minimal safety picture, but with annotations doing the heavy lifting, the bar is met. It does not describe what a conversation form is or any kind of filtering behavior.

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?

A single short sentence with no wasted words and clear front-loading of the action. Efficient for a simple read-only tool, though slightly over-terse in that it omits any distinguishing context.

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?

Adequate for a simple tool with 1 optional parameter, no output schema, and annotations covering safety. However, it lacks any explanation of what conversation forms are, how they relate to Facebook ad pages, or how this differs from lead-form retrieval, leaving some ambiguity for an agent.

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 the single locationId parameter already documented ('Location identifier Defaults to GHL_LOCATION_ID when omitted'). The description adds nothing about parameters, so the baseline 3 applies since the schema carries the full burden.

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?

States a clear verb-resource pair ('Get conversation forms') that adequately conveys the operation. However, it does not differentiate from adjacent siblings like ad_manager_fb_get_page_lead_forms and ad_manager_fb_get_lead_form, which an agent could easily confuse with conversation forms. The description is clear but borders on merely expanding the tool name suffix.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., get_lead_form vs. get_page_lead_forms vs. get_conversation_forms). No exclusions, no context about which Facebook object this maps to, and no mention of prerequisites such as a configured integration.

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