ghl_ad_li_lead_form_create

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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). Description adds OAuth scope requirement ('adPublishing.write'), which is useful, but does not elaborate on creation behavior, idempotency, or side effects.

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?

Description is moderately concise but contains redundancy (first line repeats title). It mixes purpose with technical details (endpoint, version, scope), which could be streamlined. No wasted words but could be shorter.

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?

Despite complex nested parameters, schema covers them fully. However, there is no output schema and the description does not mention return values, response structure, or prerequisites (e.g., required integrations). This gap reduces completeness 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 descriptions already provided for all parameters. The tool description does not add further parameter insights beyond what the schema offers, so 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?

Description clearly states the action ('Create a new LinkedIn lead gen form for an ad account'), identifying the specific resource and platform. Distinguishes from sibling tools like Facebook lead form creation by explicitly mentioning LinkedIn.

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 explicit guidance on when to use this tool versus alternatives. The context is implied from the name and sibling set (e.g., for LinkedIn vs Facebook), but no when-not-to-use or comparison is provided.

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