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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is fully covered; the description's closing 'Read-only' merely restates it. It adds some content-level context (what lead fields and attribution come back, and the recency behavior of 'since'), but return values are also covered by the output schema, so net new disclosure is modest.

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 core purpose and free of padding; the second sentence efficiently bundles parameter sourcing and the incremental-pull idiom. Slight redundancy in the dangling 'Read-only' clause, but overall tight and well-ordered.

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?

With a 3-param schema (one required), full annotations, and an output schema that covers return values, the description supplies enough to invoke correctly: form_id source, since semantics, and the returned data shape. Only the un-documented limit param and lack of pagination notes keep it from being exhaustive.

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 the load: it documents where form_id comes from (list_meta_lead_forms) and the format/behavior of since (YYYY-MM-DD, returns only newer leads). The limit parameter and its default of 100 receive no explanation, leaving one of three params 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 ('Downloads the answers people submitted through a Meta instant form') and enumerates the returned content (name, phone, email, custom questions, plus ad/adset/campaign attribution). It also distinguishes itself from siblings by naming the tiktok counterpart and the list_meta_lead_forms source tool, so an agent can separate it from the many other lead 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?

Routes the agent to list_meta_lead_forms for obtaining form_id and explains the incremental-pull pattern ('since returns only newer leads, which is how you pull just what arrived since the last check'). No explicit exclusions or when-not-to-use guidance, but the primary usage path is clear.

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