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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), and the description adds ordering ('newest first'), payload content ('with their answers'), and a privacy handling constraint that no annotation conveys. It stops short of describing pagination/volume behavior or whether an unfiltered call returns all forms' leads.

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?

Two short sentences, front-loaded with the resource and ordering, followed by the dependency pointer. The parenthetical privacy note is compact; nothing is redundant with the title, though the phrasing is slightly fragmented.

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?

With no output schema, the description usefully sketches the return payload (leads plus their answers) and ordering. For a five-parameter, zero-required read tool it is nearly sufficient, missing only guidance on defaults when no lead_form_id or account is supplied.

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%, below the high-coverage threshold, so the description must carry some weight. It meaningfully clarifies lead_form_id by telling the agent where to obtain it, but limit, folder, account, and language semantics are left entirely to the schema, including the 1-100 cap and the Arabic/enum rule.

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?

Names the exact resource (leads submitted through LinkedIn Lead Gen Forms) and the ordering guarantee (newest first). It also distinguishes itself from the adjacent metadata tool by pointing to linkedin_lead_forms, so an agent can pick between listing leads and listing forms without opening either schema.

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?

Gives a concrete prerequisite: find lead_form_id with linkedin_lead_forms before calling. It also flags a handling rule for personal data ('show only to the user'). No explicit exclusions or when-not conditions are stated, keeping it just short of a 5.

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