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

With no annotations, the description carries the behavioral burden. It discloses that the data is 'public' and that results are sorted by follower count with a 'max 20' cap, which suggests a read-only directory operation. However, it does not mention pagination behavior, whether the operation requires authentication, or what fields are returned.

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 single sentence is compact, front-loaded with the core purpose, and avoids wordiness. It earns its place by conveying resource, scope, ordering, and a limit, though it leaves behavioral details absent.

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 paginated list tool with three parameters and no output schema, the description is too sparse. It omits guidance on cursor usage, per_page semantics, response shape, and how the tool differs from search_content — all of which an agent would need to invoke it correctly.

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 67%, with page and cursor documented in the schema. The description adds context by indicating follower-count ordering and a max of 20 results, which aligns with per_page's maximum. It does not add meaningful detail about how page, cursor, or per_page interact.

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 clear verb ('Browse'), a specific resource ('the public NudiTok creator directory'), and an ordering criterion ('by follower count'). It distinguishes this from the sibling tools by identifying the resource as a directory of creators, though it does not explicitly contrast it with search_content or get_user.

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 guidance is provided about when to use this tool versus alternatives such as search_content or get_user. The description implies a browsing use case but does not state exclusions, preferred scenarios, or relationships to sibling tools.

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