tiktok get async report status

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

Given the rich readOnly/idempotent/destructive annotations, the bar is lower; the description adds a useful caveat that no report creation or mutation is performed, which is slightly beyond the annotation. However, it doesn't disclose polling behavior, error semantics, or availability details, so it adds only modest behavioral context.

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 succinct sentences with no filler. The main lookup action and the read-only caveat are front-loaded, making the description easy to scan.

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 complete parameter descriptions, an output schema, and strong annotations, the description covers most of what the agent needs. The only notable gap is the vague 'when async report endpoints are available' condition, which is not elaborated.

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%, with both taskId and advertiserId documented in the input schema. The description only repeats 'by taskId' and adds no semantic value beyond the schema, so it earns the baseline 3.

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 uses a specific verb ('Check') and resource ('TikTok async report task status') and identifies the lookup key (taskId). It is clear about what it does, but it doesn't explicitly differentiate from sibling tools or name an alternative, so it stops short of the highest rating.

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 provides a rough condition ('when async report endpoints are available') and disclaims mutation, but the condition is undefined and no alternative tool is named for creating or mutating reports. The use case is implied rather than explicitly contrasted with alternatives.

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