Profile

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

Adds materially beyond the annotations: it discloses paid credit consumption, the confirm=true gate, and reassures that read-like POST requests do not publish to social platforms (which resolves the otherwise confusing readOnlyHint=false). Cache behavior is delegated to the schema's cache_max_age description. It does not discuss rate limits or failure modes, so not a 5.

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?

Front-loads purpose, then return shape, then scope exclusion, then cost/safety caveats. The enumeration of user and stats fields is somewhat verbose but justified because no output schema exists. Every sentence carries information; no filler.

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, the description usefully sketches the return payload and covers the credit/confirm caching constraints an agent must respect. It leaves the handle-vs-user_id selection rule and error/empty-result behavior unspecified, which is a minor gap for a 5-parameter tool.

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 100%, so the schema already documents handle, user_id, account, confirm, and cache_max_age, including the enum and credit implications. The description adds little per-parameter meaning beyond the identity use case, so the baseline 3 applies.

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?

States a specific verb and resource (fetch public TikTok profile data by handle or user_id) and enumerates the returned payload (user + stats objects). It explicitly carves out scope boundaries against siblings: 'This only returns profile metadata, not the user's actual videos or followers list,' which separates it from tiktok_profile_videos and tiktok_followers.

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?

Gives a clear use case (looking up a creator's identity, bio, account stats) and an implicit exclusion via the scope note about not returning videos or followers, which routes agents to tiktok_profile_videos / tiktok_followers. It stops short of naming those alternatives explicitly or stating prerequisites for choosing between handle and user_id.

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