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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds genuinely new behavior: reading forms works with normal ads permissions, whereas downloading leads requires LinkedIn's separate Lead Sync API access — useful operational context not present in structured fields.

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?

Three tight sentences, front-loaded with what is returned, followed by usage routing and permission caveat. No filler or restatement of the title.

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 values need not be documented, yet the description still lists key fields. Scope, sibling routing, and the permission distinction between reading forms and downloading leads make it complete for a single-parameter read 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?

There is one parameter (account_id) with 0% schema description coverage. The description implies it by saying the forms belong to 'an ad account' but never states the expected id format or where to get it (e.g., list_linkedin_ad_accounts). Adequate but leaves a gap the schema does not fill.

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 (Lists) plus resource (LinkedIn Lead Gen Forms) scoped to an ad account, and enumerates the returned fields (id, name, status, question count). It is clearly distinguishable from sibling listers such as list_meta_lead_forms, list_tiktok_lead_forms and from download_linkedin_leads.

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?

Explicitly says when to use it ('find which form a lead-gen campaign collects into before pulling the leads') and names the alternative tool (download_linkedin_leads) for the next step. It also states the prerequisite permissions, so the agent knows the routing and the access condition.

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