list_lead_forms

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

There are no annotations, so the description must carry the full transparency burden. It merely says 'List', implying a read-only operation, but it does not disclose whether archived lead forms are included, pagination behavior, ordering, or how missing/invalid ad_account_id is handled.

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, front-loaded sentence with no redundant words. It is appropriately concise for what it states, though it sacrifices necessary detail for brevity.

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 input schema is simple and there is no output schema, so the description should fill gaps about return values, pagination, and optional/required behavior of ad_account_id. It does none of that, leaving an agent with insufficient information to invoke the tool confidently.

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 description coverage is 0%, and the description only says 'for the ad account' which adds little beyond the parameter name 'ad_account_id'. It does not explain the parameter format, whether it is optional, or which account is used if omitted.

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 has a specific verb ('List') and a clear resource ('Lead Forms') plus the ad-account scope, making the operation identifiable. It doesn't explicitly differentiate from sibling tools like get_lead_form or list_lead_sync_subscriptions, but the resource name is distinct enough.

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?

No guidance is provided about when to use this tool versus alternatives such as get_lead_form, create_lead_form, or list_lead_sync_subscriptions. The intended use is only implied by the word 'List' and the resource name.

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