leads_list_forms

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

No annotations are provided, so the description must convey behavioral traits. It only says 'List', implying a read-only operation, but fails to disclose pagination behavior, the presence of a limit parameter, rate limits, or the response structure. For a tool with zero annotation coverage, this is insufficient.

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 single, concise sentence that gets straight to the point. It is front-loaded with the action and resource, and every word contributes value. Nothing is bloated or irrelevant.

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 simple listing tool, the description is minimally adequate, but it leaves gaps: no output schema, no parameter details, and no mention of pagination. The absence of behavioral and parameter context makes it less complete than it could be, though the core purpose is clear.

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 descriptions are completely absent, and the description does not explain either parameter. The phrase 'attached to a Page' vaguely maps to page_id, but the limit parameter is entirely unaddressed. The description fails to compensate for the 0% schema coverage.

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?

Clearly states the verb 'List', the resource 'lead generation forms', and the scope 'attached to a Page'. This distinguishes it from sibling tools like leads_list_from_form (which lists leads from a form) and leads_get_form (which retrieves a single form).

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 the tool is used when needing forms for a specific page, but it does not explicitly state when to prefer it over alternatives or mention any exclusions. No alternative tools are referenced, so usage guidance is left to inference.

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