meta_ads_lead_forms_get

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

Declares 'Read-only' and lists the return fields in detail, which is sufficient for a fetch operation. No annotations exist, so the description carries the full burden and handles it well.

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?

Four concise sentences: action, return fields, read-only note, usage advice. No redundancy, front-loaded with key information.

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?

Given no output schema, the description thoroughly enumerates return fields and explains the tool's purpose, making it complete for a detail fetch tool.

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%, providing definitions for both parameters. The description adds context by noting form_id comes from meta_ads_lead_forms_list, adding value beyond the schema.

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 states the verb 'Fetches' and the resource 'full detail record for a single lead form', listing key return fields. It distinguishes from sibling meta_ads_lead_forms_list by implying this is for details of a specific form.

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?

Provides explicit usage guidance: 'Call this before designing downstream CRM sync so you know the exact field keys to map.' Though it doesn't explicitly state when not to use it, the context makes it clear it's for detail retrieval.

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