zuckerbot_lead_forms

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

No annotations are provided, so the description fully compensates by explaining listing behavior, selection, and persistence for future launches. It does not mention error handling or limitations, but overall provides adequate behavioral context.

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 sentences cover all necessary information: listing, selection, and usage context. No redundancy or wasted words.

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?

Given a single optional parameter and no output schema, the description is sufficient for an agent to understand when and how to use the tool. It explains the business reason for selection (reuse CRM form) and the two modes of operation.

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% and defines select_id clearly. The description reinforces that omitting it lists forms and providing it selects one, but adds no new detail beyond the schema, resulting in a baseline score.

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 clearly states it lists Meta lead forms, shows which is currently selected, and optionally selects one by providing select_id. This distinguishes it from sibling tools that deal with other aspects of Meta advertising (e.g., audience creation, campaign insights).

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?

Explicitly advises to use before launching a leads-objective campaign to reuse a CRM-connected form, avoiding unnecessary new form creation. While it doesn't list alternatives, the context makes the recommendation clear.

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