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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the exact return contents and the fact that page_id is the join key for download_tiktok_leads.

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 sentences, no filler, with the resource scope front-loaded and the workflow hint immediately after. Every clause earns its place.

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 an output schema present and annotations covering safety, the description is nearly complete for a simple list tool. The only gap is the undocumented advertiser_id parameter, which no other structured field explains.

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?

The single parameter advertiser_id has 0% schema description coverage and the description never mentions it. With an undocumented parameter and no compensating text, the definition leaves the agent to infer what identifying value to pass.

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 (lists) plus a specific resource (TikTok LEAD-GEN instant forms) and even names the fields returned (page_id, title, status, creation time). It distinguishes itself implicitly from list_lead_form_submissions and get_tiktok_lead_form_fields by scoping to forms rather than submissions or fields.

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?

Explicitly places the tool in a workflow: find the forms before pulling leads, and names download_tiktok_leads as the consumer of the page_id. It does not address when to use get_tiktok_lead_form_fields instead, so exclusions are incomplete.

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