Update a TikTok profile

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

No annotations are provided, so the description must carry the full burden of behavioral transparency. It only mentions that the update happens 'through the local browser', but fails to disclose side effects, permission requirements, reversibility, or any potential impact on the account. It is a mutation tool with no safety or behavior details.

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 is direct and to the point. It provides the essential information without unnecessary words, fitting the tool's simple purpose.

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 mutation tool with no annotations and no output schema, the description is too sparse. It does not mention prerequisites (e.g., a connected browser), error scenarios, or what happens after the update. Given its low complexity, more context is needed to be considered complete.

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 only 33% (only account_id has a description). The tool description mentions 'display name' and 'bio' but adds little beyond the parameter names themselves; it does not explain constraints, formats, or optionality beyond what the schema already shows. The phrase 'or both' hints at combinability but is only minor extra value.

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 action ('Update') and the specific resources ('display name, bio, or both'), with a mechanism ('through the local browser'). It distinguishes itself from sibling tools like tiktok_update_avatar by focusing on profile text fields rather than avatars.

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 use case is implied: when you need to update profile display name or bio. However, there is no explicit guidance on when not to use it or which sibling tool to use instead (e.g., tiktok_update_avatar for profile pictures). No exclusions or alternatives are mentioned.

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