ad_manager_li_create_lead_form

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the agent knows it's a non-idempotent mutation. The description adds nothing beyond the verb 'create' — no disclosure of side effects, required account context, or consequences. It does not contradict annotations, but fails to provide behavioral context beyond what the verb implies.

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 a two-word phrase that is extremely sparse. It lacks structure and does not front-load any important caveats or context. This is under-specification rather than useful conciseness.

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 tool with 6 required parameters, nested objects (content, owner, creationLocale), and no output schema, a two-word description is entirely inadequate. The agent receives no explanation of what a lead form entails, how to structure the content, or what the expected outcome is. This is far from 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 description coverage is 100% — each of the 8 parameters has a description. The tool description adds no parameter-level meaning, so it relies entirely on schema. Baseline 3 is appropriate given full schema coverage.

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 states a clear verb and resource: 'Create lead form'. This distinguishes it from siblings like ad_manager_li_get_lead_forms (create vs get). However, it doesn't explicitly differentiate from other creation tools such as ad_manager_fb_create_page_lead_form, though the platform is implied by the name.

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. There is no mention of use cases, prerequisites, or when to prefer this over other lead form creation tools. The description is purely a verb+noun with no contextual instruction.

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