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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered elsewhere. The description adds useful context by disclosing the returned fields (id, name, status) and the lead-ad/launch-objective scope, but says nothing about pagination, page ownership requirements, or error behavior (e.g., invalid page_id).

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?

Two short sentences, front-loaded with the resource and scope. The parenthetical '(lead forms)' and the restatement of 'instant forms of a page' in sentence two are mildly redundant but not wasteful.

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?

A simple one-parameter read tool with no output schema; the description lists the fields returned and the business context, which is enough for an agent to call it correctly. Only pagination/result-size behavior is unaddressed, a minor gap.

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% and the single page_id parameter is documented in the schema, including a pointer to list_pages and a numeric pattern. The description adds no semantics beyond that, so the baseline 3 applies.

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+resource: lists Meta instant forms (lead forms) belonging to a Facebook page. It also names the fields returned (id, name, status), which lets an agent distinguish this from siblings like list_pages or get_launch_questions. It stops short of explicitly contrasting with any named sibling.

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?

Usage context is implied rather than stated: 'for lead ads' and 'for a launch with a Leads objective' tell the agent the scenario, but there is no explicit when-to-use/when-not guidance or reference to an alternative tool for related data.

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