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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is known. The description adds meaningful behavioral context beyond that: the lead-sync permission is granted at authorization time, a specific reconnection error requires an exact user-facing response, and the operation is free. No contradiction with annotations exists.

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 front-loaded with the resource and return fields, and each subsequent sentence adds context: creation source, read-only nature, error handling, and cost. It is slightly dense and repeats the read-only point in more than one place, but it remains under ~65 words and earns its length.

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?

There is no output schema, so the description appropriately compensates by naming the return fields (id, name, state, version, form fields). It also covers ownership scope, how forms come to exist, authentication permission timing, and read-only/free behavior. For a list-style tool with two optional parameters, this is complete enough for an agent to invoke it correctly.

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 both pageId and adAccountId are already well explained in the schema. The description's mention of 'Page or ad account' aligns with the parameters but does not add meaning beyond what the input schema already provides. The baseline of 3 is 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 clearly identifies the verb and resource: it lists LinkedIn lead gen forms owned by a Page or ad account, and it enumerates what is returned (id, name, state, version, requested fields). It also distinguishes itself from creation by stating this API only reads and cannot create a form, which separates it from related lead-related sibling tools.

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 description gives a clear context for use: retrieving lead gen form definitions owned by a Page or ad account, and it explicitly notes that forms are created elsewhere (Campaign Manager or the Page), so this tool is not for creation. It lacks an explicit 'for actual leads, use list_linkedin_leads' style exclusion, but the context is strong enough for an agent to route correctly.

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