tiktok_profile: GET /

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly states the operation is a fetch of public data and enumerates the response fields, but it does not mention behavior around errors, non-existent handles, rate limits, or data freshness. For a benign read operation this is acceptable but has 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?

The core behavior and return fields are packed into a single dense sentence, followed by a concise list of use cases. The opening line 'Get TikTok Profile' is somewhat redundant with the title, but the overall description is lean, informative, and front-loaded.

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 a single well-documented parameter and no output schema, the description compensates by listing the contained fields. It gives enough context for an agent to construct a correct call and interpret the result. It could optionally cover failure cases or input validity expectations, but the essentials are present.

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%, so the sole required parameter 'handle' is fully documented in the schema, including the '@' detail. The description repeats 'username (handle)' without adding significant new meaning. Baseline 3 is appropriate when the schema already carries the weight.

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 states a specific verb ('Fetches'), resource ('public TikTok profile'), and identifier ('username (handle)'). It also explicitly lists the returned fields, making the tool's function unmistakable. Sibling names like comments/posts/search make this profile-focused tool clearly distinct.

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 provides concrete use cases: enriching CRM/lead records, verifying influencer reach, watching competitor accounts, and building metadata datasets. It clearly implies this tool is for profile-level lookups, though it does not explicitly state when to use alternative sibling tools.

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