List connected TikTok accounts

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

The description adds a non-obvious behavioral trait beyond the annotations: this tool does not call TikTok at all, so it succeeds even when a token has expired. This meaningfully informs the agent about network dependency and failure modes. Annotations already cover read-only and idempotent safety, so the description's extra context earns credit.

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 tightly written sentences deliver the core purpose, the practical use of the result, and a key behavioral guarantee. There is no filler or redundancy.

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?

Given the tool's simplicity, empty schema, and strong annotations, the description covers everything an agent needs: what the tool returns, how to use the result, and an important edge-case behavior. No output schema exists, but the description states the essential return semantics.

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?

The tool has zero parameters and the schema already defines an empty object, so there is nothing for the description to add. The description still clarifies what the returned value serves as (`account` on other tools), which is useful semantic context for an otherwise parameterless call.

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 clearly identifies the resource: all TikTok accounts the server can act as, and distinguishes this from sibling tools by stating these account names are the values to pass as `account` elsewhere. The purpose is specific and immediately actionable.

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 description gives clear context for when to call this tool: when you need the canonical account identifiers to use with any other tool. It also notes that it works even with an expired token, implying it is safe to use as a fallback or first step, though it does not explicitly list exclusions or alternatives.

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