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 does add useful behavioral context: the data model limitation (TtUser lacks IG-style fields) and the security warning that returned content is user-generated and untrusted. It omits pagination behavior, result ordering/tie-breaking, and any auth or rate-limit requirements.

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?

Two tightly packed sentences with the core purpose front-loaded and the differentiator/security caveat following. Minor jargon ('T4 inserter design') costs a little readability but wastes no space.

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 listing tool with no output schema and full schema coverage on inputs, the description is nearly sufficient: it covers purpose, ranking dimensions, scope limits, and the untrusted-input caveat. It could add a note on returned fields or result ordering, but what is present addresses the agent's main decision points.

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 all four parameters (limit, sort_by, min_followers, verified_only) are already fully documented in the schema, including the enum mapping for sort_by. The description's mention of ranking dimensions maps to sort_by but adds no syntax or default detail beyond the schema. Baseline 3 is appropriate.

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+resource ('Get top TikTok users') and the exact ranking dimensions (follower / heart / video count). It explicitly separates itself from the sibling get_top_users by noting the absence of IG-style category/country/face-detection filters. An agent can distinguish it from other top-user tools without opening the schema.

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?

Clarifies the context in which this tool applies (TikTok-native ranking) and explains why IG-style filters are unavailable, which implicitly routes the agent here for TikTok rather than the generic get_top_users. It does not, however, explicitly name the alternative or state when NOT to use it.

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