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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: it requires LinkedIn's Lead Sync API access and warns that the tool reports when the account has not been reconnected since the permission was granted. It stops short of describing pagination or what limit=200 means in practice.

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?

A tight paragraph that front-loads what is downloaded, then parameter meanings, then the access prerequisite. Every clause earns its place and nothing is repeated from the schema or annotations.

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?

An output schema exists, so return formatting need not be explained, and the description still covers data scope, filtering, and the permission/reconnection failure mode. Only the limit/pagination dimension is left unaddressed for a 6-parameter 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 description coverage is 0%, so the description must carry the load, and it clarifies form_id's source, the YYYY-MM-DD format for since/until, and the meaning of test_only. It leaves 'limit' (default 200) undefined, which is the one meaningful gap among the non-obvious parameters.

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?

States a specific verb and resource ('downloads the leads submitted through LinkedIn Lead Gen Forms') and enumerates the payload (name, email, phone, every other answer). It is immediately distinguishable from list_linkedin_lead_forms and from its download_meta_leads / download_tiktok_leads siblings without opening the 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 clear routing context: form_id comes 'from list_linkedin_lead_forms', and test_only=true is scoped to leads generated from Campaign Manager. It does not state when *not* to use this tool or address overlap with list_lead_form_submissions, so it falls short of explicit alternatives/exclusions.

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