Get Leads from Form

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

Annotations already indicate read-only behavior. The description adds context that it returns 'lead data including field values, creation time, and ad info.' No contradictions. It does not disclose rate limits or pagination details beyond the cursor param.

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 concise and well-structured: main purpose first, then prerequisite, then parameter list. Every sentence provides necessary information without 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?

Given no output schema, the description explains return values. It covers all required parameters, pagination, and limit. The response_format parameter is only in the schema, which is acceptable as it's optional. Overall, it is complete for a read-only 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?

Schema coverage is 60% (3 of 5 params described). The description adds meaning: it clarifies that form_id comes from meta_list_leadgen_forms, page_id is for authentication, and limit has a range/default. It also describes return data, compensating for the absence of an output 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 clearly states 'Gets submitted leads from a lead generation form,' specifying the verb (gets), resource (leads), and source (from a lead gen form). It distinguishes itself from sibling tools by targeting a specific entity.

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 explicitly lists a prerequisite: 'Requires: meta_list_pages must be called first to load page tokens.' It provides param details but does not explicitly state when to avoid this tool or alternatives. However, it implies correct usage by specifying dependencies.

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