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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the trailing "Read-only" is largely redundant. The description does add that the response enumerates each form's questions, which is useful behavioral context, but it never mentions pagination or how the limit default of 50 behaves.

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?

Front-loaded with the purpose, followed by usage and the parameter provenance, with no filler prose. The final "Read-only" clause duplicates the annotations and could be dropped, which is the only real waste.

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 the description needn't detail return values, and it adequately covers when to call the tool and where the required page_id comes from. The notable gap is pagination/limit behavior, which an agent would need when a Page has many forms.

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 parameter meaning. It does explain the origin of page_id (from list_meta_pages), which the schema does not, but the limit parameter is left entirely unexplained, so half of the parameters remain undocumented.

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 (lists Meta/Facebook instant lead forms), and scopes it to a Page, immediately distinguishing it from create_meta_lead_form, list_lead_form_submissions, and the LinkedIn/TikTok lead-form siblings. The returned fields (id, name, status, questions) further pin down what kind of listing this is.

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 concrete downstream usage: retrieve the lead_gen_form_id to pass into create_meta_link_ad / create_meta_video_ad, or to inspect an existing form before reuse, and notes page_id originates from list_meta_pages. It stops short of naming the sibling to avoid (e.g. create_meta_lead_form, list_lead_form_submissions), so it is clear context rather than full when/when-not routing.

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