publish_lead_form

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It reveals the action and one post-condition, but does not mention irreversibility, side effects, permission requirements, or what happens to an already-published form.

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 short sentences with the primary action front-loaded. Every word contributes meaning and there is no filler or redundancy.

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 tool has no annotations and no output schema, so the description needs to explain enough for a correct call. It omits what ad_account_id is for and does not state expected behavior on success or failure, leaving meaningful gaps for a mutation tool.

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?

The schema describes lead_form_id only as 'Lead form ID.' and leaves ad_account_id completely undescribed. The description does not compensate for this gap or clarify the role of either parameter, especially ad_account_id.

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 the specific action 'publish' and the resource 'Lead Form draft,' and clarifies the intended consequence: the form can then be attached to a Business Agent. This separates it from sibling tools like create_lead_form, update_lead_form, and publish_business_agent.

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 implies usage: publish a draft lead form before attaching it to a Business Agent. However, it does not explicitly state when not to use this tool, what prerequisites exist, or how it compares to update_lead_form or create_test_lead_submission.

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