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

No annotations are provided, so the description carries the full burden. It usefully discloses two non-schema behaviors: a cost of 1 credit and a required Authorization: Bearer <api_key> header. It says nothing about rate limits, failure modes, or whether the profile must be public-facing beyond 'public', leaving gaps.

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?

Purpose is front-loaded, which is good, but the definition is padded with metadata-style boilerplate ('Platform=tiktok resource=user') that duplicates the tool name, and there is a stray double period after 'avatar.'.

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 read tool with no output schema and no annotations, the description covers the essentials: what it fetches, the returned fields, the auth requirement, and the credit cost. Missing only error/rate-limit behavior, which is minor here.

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 single username parameter already documents format ('without @') with an example. The description only restates 'by username', adding no format or edge-case detail beyond the schema, 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 (Fetch), resource (public TikTok profile), and scope (by username), plus the fields returned (bio, stats, verification, avatar). This clearly separates it from tiktok_posts, tiktok_post, and tiktok_search, though it never names a sibling explicitly.

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?

No when-to-use guidance, no conditions for choosing this over tiktok_posts or tiktok_followers, and no exclusions. The only guidance is operational (cost and auth), not selection-oriented.

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