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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing the operation's safety profile. The description adds value by enumerating the returned fields (bio, verification, counts, engagement stats) and noting the API key requirement. However, it does not disclose additional behavior such as rate limits, pagination, or error handling. With annotations covering the core behavior, a 3 is appropriate.

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 exceptionally concise: two sentences that front-load the core purpose, then specify the input variations and an inline example. Every sentence earns its place without redundancy. The example call is compact and directly illustrates the parameter usage, making it immediately actionable for an agent.

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 carries the burden of explaining return values, and it does list the key fields (bio, counts, engagement stats). It also clarifies the two input alternatives and the API key requirement. However, it omits any mention of error responses, rate limiting, or what happens when the handle/user_id is invalid. These are minor given the idempotent read-only nature, but a more complete description would note such edge behaviors.

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% — all three parameters have descriptions in the input schema. The description reinforces the meaning of 'handle' and 'user_id' but adds no new semantic detail beyond including an example. It correctly illustrates usage patterns (e.g., 'stoolpresidente') but does not elaborate on edge cases or format constraints. This meets the baseline for high schema coverage.

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 is specific and actionable: it names the exact resource (TikTok creator profile), lists the data returned (bio, verification, counts, engagement stats), and specifies the two accepted input methods (handle or user_id). This clearly distinguishes it from sibling tools that target other platforms (Facebook, Instagram, YouTube).

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 usage through the tool name and input explanation, but it does not explicitly state when to choose this tool over alternatives or when not to use it. The sibling tools address other social platforms, so context is inferable, but there is no direct 'use this when…' guidance. An example call is provided, which helps, but usage exclusions are absent.

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