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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that: newest-first ordering, inclusion of lead answers, and a privacy instruction to show lead data only to the user. It does not cover whether results are paginated beyond limit or what happens when no form is specified.

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 short sentences, front-loaded with the purpose before the parameter hint and the privacy caveat. Every sentence carries information, though the personal-data sentence is guidance rather than tool behavior and could have been folded more tightly.

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 9-parameter tool with no output schema, the description is adequate but thin: it does not explain how a caller identifies which form/ad to pull leads from, despite form_id, page_id, ad and folder all existing as selectors. The ordering and privacy notes help, but the selection workflow is left implicit.

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?

With 67% schema description coverage, the schema already documents since, detail, folder, account, page_id and language. The description reinforces the meaning of since ('only new leads'), which the schema only formats as YYYY-MM-DD, adding a real semantic cue. It says nothing about limit's 1–500 bound, ad, or form_id.

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 states a specific verb and resource ('Get the leads submitted to a lead form (or a lead ad)') plus the return ordering ('newest first, with their answers'), so an agent knows exactly what it retrieves. It does not explicitly differentiate itself from the sibling meta_lead_forms, leaving ambiguity about which tool lists forms versus which lists submissions.

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?

It gives one concrete usage hint ('Use since to get only new leads') and a handling constraint about personal data. However, it never states when to choose this over meta_lead_forms or linkedin_get_leads, nor any prerequisite such as needing a form_id or page_id first.

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