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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. Beyond that, the description adds only account scoping and says nothing about what is returned (a form list?), whether forms are per-campaign or account-wide, or pagination — with no output schema, that gap matters.

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?

A single short sentence with no filler, and the resource is front-loaded. The phrasing is a noun fragment with an awkward comma splice, which slightly undercuts readability, but nothing is wasted.

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?

The tool is simple (3 optional, fully documented params, no output schema, read-only annotation), yet the one thing an agent most needs — whether this lists or creates forms — is absent. That missing verb is a material ambiguity for a form-related tool in an account full of lead-gen tooling.

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 all three parameters are optional, so the schema already explains folder, account, and language. The description contributes no additional meaning about these parameters, which meets the baseline-3 expectation when the schema carries the load.

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 names the resource ("Instant (lead) forms") and scopes it to an advertiser, but never supplies a verb — it is ambiguous whether the tool lists existing forms, retrieves a single form, or creates one. Siblings such as meta_lead_forms and linkedin_lead_forms are not distinguished, though the "tiktok_" prefix does the platform disambiguation.

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?

The clause "needed for lead-generation campaigns that collect leads inside TikTok" hints at relevance but gives no explicit trigger, prerequisites, or exclusions. It does not tell the agent when to pick this over meta_lead_forms, linkedin_lead_forms, or the *_get_leads tools that likely operate on the submissions these forms collect.

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