create_lead_form

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

With no annotations, the description carries the behavioral burden. It usefully discloses that the result is a draft and that publishing is a separate later step, and it summarizes required field constraints. However, it does not disclose auth/permission needs, reversibility, or what the response returns.

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?

Two tight sentences with the core verb, resource, validation constraints, and next-step workflow all present. No filler or repetition of every schema property.

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 plus rich schema covers required inputs and the draft/publish workflow. The lack of an output schema and annotations is partially mitigated by the clear draft-state note, though a hint at the returned object would make it fully 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 coverage is 80%, so the schema already explains most parameters. The description condenses the required name/fields rules accurately but adds no meaning beyond the schema; optional parameters such as ad_account_id and privacy_policy_url are left entirely to the schema.

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 specific action ('Create a draft Lead Form') and target resource, and adds 'Publish after creation' to mark lifecycle stage. This clearly separates it from sibling tools like publish_lead_form, update_lead_form, and list_lead_forms.

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?

'Publish after creation' implies a workflow and distinguishes this creation step from later publishing, but it does not explicitly name the alternative tool or state when this tool should be used instead of update/publish. Usage context is implied rather than explicit.

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