ad_manager_fb_create_conversation_form

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

Annotations indicate readOnlyHint=false, confirming a write operation, but the description adds no behavioral context beyond that. It does not disclose side effects, required permissions, integration dependencies, or any other operational details. With no additional context, the description provides no value beyond what annotations already convey.

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 but at the cost of substance. It is a single sentence that merely restates the tool name, offering no useful information to the agent. While it is brief, it is not effectively structured to front-load any actionable details, making it under-specified rather than appropriately concise.

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?

For a mutating tool with four parameters and no output schema, the description is grossly insufficient. It does not explain what a conversation form is, how it fits into the ad manager workflow, or what the expected outcome is. The lack of any contextual detail makes it impossible for an agent to determine when and how to use this tool correctly.

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 description coverage is 100%, so all four parameters have their own descriptions. The tool description adds no parameter information, but per the rubric the baseline is 3 when the schema is thorough. The description does not enhance understanding of parameters like 'questions' or 'locationId' beyond what the schema already provides.

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 'Create conversation form' is a near-tautology of the tool name, restating the verb and resource without adding clarity. It does not differentiate this tool from the closely related sibling ad_manager_fb_create_page_lead_form, which also creates a form. The description fails to specify the unique purpose or scope of a conversation form.

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 contains no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or scenarios where a conversation form is appropriate compared to page lead forms or other ad manager creation tools. An agent receives zero directional information.

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