List scheduled TikTok posts

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

No annotations are provided, so the description carries the full burden. It discloses that posts are 'recorded by this local MCP', which is a useful caveat about local caching. However, it does not mention the default behavior of include_done, return format, or any side effects, leaving important behavioral gaps.

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?

A single sentence with no redundancy. The verb is front-loaded and the sentence is efficiently structured, making it 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 no output schema and no annotations, the description should explain return values and parameter meanings. It only states the high-level purpose, leaving the agent without crucial details about what the tool returns or how parameters affect behavior.

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 0%, and the description makes no mention of account_id or include_done. The parameter names are somewhat self-explanatory, but the description adds no meaning beyond the bare schema, failing to compensate for the lack of schema descriptions.

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 ('List') and resource ('native scheduled posts') with an added scope ('recorded by this local MCP'). This clearly distinguishes it from the sibling 'tiktok_cancel_scheduled', which is about cancelling rather than listing.

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 context is clear: this tool lists scheduled posts. While it implies it is the read-only counterpart to tiktok_cancel_scheduled, it does not explicitly name alternatives or exclusions. Still, the purpose is unambiguous enough for basic usage.

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