tiktok_get_targeting_catalog

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It communicates read-only intent with 'Read,' but omits response shape, pagination, per-catalog behavior variation, whether advertiserId is needed, and any other operational details that matter for a generic endpoint wrapper.

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?

The entire description is one efficient sentence that front-loads the action and scopes the resource, then packs in the complete catalog inventory without filler. The length is justified by the need to enumerate many catalog types.

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 has a complex shape — a nested `parameters` object, no output schema, and many catalog-specific variants — yet the description only lists catalog names. It doesn't explain how to compose requests, when to supply `query`, what `parameters` should contain, or what the agent should expect back, making it insufficient for reliable invocation.

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 only 25%, and the required `catalog` parameter lacks a schema description. The description does add some value by translating catalog enum values into human-readable categories, but it says nothing about `query`, `parameters`, or `advertiserId`, so the agent is left guessing on most parameters.

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?

Starts with a clear verb+resource ('Read TikTok targeting and planning catalogs') and enumerates the specific catalog categories, which maps closely onto the enum values. It doesn't explicitly distinguish itself from similar read endpoints like tiktok_search_keywords or tiktok_get_read_endpoint, so it stops short of a 5.

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?

There is no guidance on when to choose this tool over sibling tools, no stated exclusions, and no mention of which catalog types work with which optional parameters. The only usage signal is an implicit 'if you need a targeting catalog,' which leaves appropriate selection to inference.

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