tiktok_get_async_report_status

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly states no mutation is performed, which is valuable, but it does not mention required auth/scope, polling behavior, or what a response contains. The read-only claim is clear but incomplete.

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 with no filler. The core purpose is first, and the anti-mutation clarification is a necessary second sentence. Every word 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?

The tool is simple, with two fully documented parameters, and the description accurately conveys the operation. However, there is no output schema and the description does not explain what status values are returned or whether repeated polling is expected, so the agent lacks full information for a correct 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 100%, giving a baseline of 3. The description adds semantic value beyond the schema by explaining that taskId comes from a TikTok report task creation outside this MCP, which clarifies where the ID originates. advertiserId is not enriched, but the provenance detail tips it slightly above baseline.

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 a concrete operation (check status), the resource (TikTok async report task), and the key identifier (taskId). It does not explicitly differentiate from sibling tools like tiktok_get_report_raw, but the 'No report creation or mutation' phrase narrows the purpose.

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 phrase 'when async report endpoints are available' gives some context and 'No report creation or mutation' implies it is for checking an already-created task. However, no alternative tool is named and there are no explicit when-to-use/when-not-to-use conditions relative to the many read-only siblings.

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