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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the kind semantics (action = behavior) and the returned pair, but says nothing about auth/advertiser scoping, pagination, or rate limits, and the output schema already documents returns.

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 dense sentence with the purpose front-loaded and the downstream consumer noted immediately after. The arrow/pipe shorthand is efficient but slightly telegraphic, costing a little readability.

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?

For a simple three-parameter read lookup with an output schema and full annotation coverage, the description supplies purpose, enum semantics, and the downstream wiring. It omits only how keyword matching works and whether advertiser_id is required to scope results.

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 coverage is 0%, so the description must compensate. It does define the kind enum values ('interest | action (behavior)') and implies an advertiser context via interest_category_ids, but the keyword and advertiser_id parameters are left entirely unexplained.

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?

Specific verb + resource: it 'searches TikTok interest/behavior targeting categories' and names exactly what comes back (id + name). The platform + category-type framing cleanly separates it from siblings like tiktok_region_search, linkedin_targeting_search, and search_meta_interests.

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?

It explicitly routes the agent into a workflow by stating the results are used as interest_category_ids in create_tiktok_adgroup, which tells the agent when to call it. There is no explicit exclusion or named alternative (e.g. region search), so it stops short of a 5.

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