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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety and reach are covered. The description adds the account scoping and the returned field set, but says nothing about result volume, pagination, or whether forms are all statuses (active/paused/archived).

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?

One compact sentence with the resource and its purpose front-loaded, and every clause carries information. The parenthetical field list is slightly clunky but earns its place by previewing the return shape.

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 read-only listing tool with no output schema, the description covers what is fetched and why, which is enough to call it correctly. The only real gap is pagination/result-size behavior, which is minor at this complexity.

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 100%, so the three parameters (folder, account, language) are already documented in the schema, including the 'optional when only one is enabled' note for account. The description adds no parameter meaning beyond that, making the baseline 3 appropriate.

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 names the specific resource (Lead Gen Forms on the ad account) and enumerates the fields returned (ID, name, status, review), so the agent knows exactly what comes back. It doesn't explicitly distinguish itself from the sibling linkedin_get_leads, though the field list implies the difference.

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 phrase 'to use as lead_form_id in lead generation ads' implies the workflow (discover form IDs before building lead gen ads), but there is no explicit statement of when to call this versus linkedin_get_leads or linkedin_ads, and no exclusions.

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