tiktok_inbox

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

No annotations are provided. The description indicates a 'refresh' action but does not clarify if it is read-only or has side effects (e.g., marking messages as read). It lacks details on authentication requirements, destructive potential, or rate limits.

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?

The description is a single sentence that efficiently conveys the tool's purpose, key benefit (no UI navigation), and return data. No unnecessary words or repetition.

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 no output schema, the description reasonably covers return fields. However, it lacks contextual details like prerequisites (e.g., user must be logged in), when to use this vs siblings, or behavior of parameters beyond what schema provides.

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%, and the description does not add parameter-specific details beyond the schema's descriptions. It mentions return fields but not parameter usage, so it meets the baseline for a fully described schema.

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 it refreshes TikTok inbox, message requests, and notification entries without UI navigation. It specifies the returned fields (username, content, conversationId, peerUid, isMessageRequest), distinguishing it from sibling tools like tiktok_reply or tiktok_im.

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 implies the tool is for reading inbox contents without UI navigation, but it does not explicitly state when to use it over alternatives like tiktok_reply or tiktok_im. No exclusions or prerequisites are mentioned.

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