refresh_token

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

With no annotations, the description should disclose behavioral traits. It mentions the stored refresh token and required config, but does not discuss rate limits, token invalidation side effects, or error scenarios (e.g., expired refresh token). This is adequate but could be more thorough.

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?

Three sentences front-load the purpose and key details. No extraneous information; every sentence serves a purpose (action, return value, requirements).

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?

For a simple one-parameter tool with no output schema, the description covers what it does, what it needs, and what it returns. It could mention potential failure modes (e.g., invalid refresh token), but defaults are covered.

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 single parameter 'account' is described beyond the schema: it explains its purpose (which account to refresh), refers to list_accounts for discovery, and notes default behavior. Schema coverage is 100%, so the description adds meaningful guidance.

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 states the tool refreshes the TikTok access token using a stored refresh token and returns new tokens. This verb-resource pairing is distinct from sibling tools like get_user_info or get_videos.

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 includes prerequisite requirements (client_key and refresh_token in account config) and references list_accounts for account selection. It does not explicitly state when not to use the tool, but the purpose is self-explanatory.

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