Get lead gen form

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that — no note on what the form object contains, whether the ID must belong to the authenticated business, or any error conditions.

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?

One very short sentence that is under-specified rather than efficient. It avoids waste but says too little to be considered well-structured for a retrieval tool.

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 no output schema and a bare description, an agent cannot know what fields come back or how to source the ID. For a read tool operating in a large sibling set, this is insufficient context.

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 single parameter lead_gen_form_id is documented only by its name and type. The description does not explain the ID format, where to obtain it, or that it must reference an existing form, leaving the schema to carry the full burden inadequately.

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 'Get a lead generation form' essentially restates the tool name and title without adding substance. It does not distinguish this retrieval tool from siblings like reddit_ads_list_lead_gen_forms or reddit_ads_create_lead_gen_form, nor does it clarify what 'getting' returns.

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?

No guidance on when to use this tool versus the sibling list_lead_gen_forms or the create variant. The agent must infer that a valid lead_gen_form_id is needed and that this is a single-record lookup.

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