zuckerbot_lead_forms

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

With no annotations provided, the description carries the full behavioral burden. It explicitly states listing is a pure read scoped to the selected Page, never changes the selection unless select_id is provided, and explains pagination via next_cursor and the result persist side effect of select_id.

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 well-structured, front-loaded set of sentences with no filler. Each sentence earns its place: the core read purpose, safety guarantee, pagination behavior, optional selection, and usage recommendation.

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 low-complexity tool with zero required params and no output schema, the description adequately covers purpose, side effects, pagination, and usage context, an agent all an agent needs to select and invoke it correctly.

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 input schema already documents both parameters comprehensively, including after as a pagination cursor and select_id as an optional selection switch. The description mostly restates the schema's semantics with some context, but does not add meaning beyond what is already in 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?

States a specific verb and resource: 'List Meta lead forms (Instant Forms)... show which is currently selected.' It clearly distinguishes from sibling tools like get_lead_form by focusing on available forms on the selected Page, and also describes the optional selection capability.

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 recommends using this 'Let's find the lead form' before launching a leads-objective campaign to reuse the CRM-connected form. It provides clear context and motivation, though it does not explicitly name alternative tools or say when not to use them.

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