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

With no annotations provided, the description carries the disclosure burden. It does convey that the result is limited to 20 items and that ranking is by engagement, which is useful. However, it does not disclose pagination behavior, whether anything is filtered by default, or any authentication/access considerations. 'Get' implies read-only but this is not explicit.

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 a single, efficient sentence that front-loads the verb and resource, then adds the key qualifiers. Every phrase earns its place: 'trending', 'adult videos', 'by engagement', 'time window', and 'max 20'.

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?

Given the output schema exists and the tool is a straightforward listing operation with no required parameters, the description is mostly complete. The main omission is any mention of how pagination should be used, though page and cursor are documented in the schema. Overall, an agent has enough information to call the tool 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 description coverage is 75%, so the schema already documents most parameters. The description adds 'max 20', but that only restates the per_page maximum already present in the schema. The phrase 'time window' maps to the window parameter but does not add new meaning beyond the enum values.

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 ('Get'), a resource ('trending adult videos on NudiTok'), and the selection criterion ('by engagement for a time window'). It is clear and distinct from sibling tools like get_user or get_video, though it does not explicitly name or contrast with get_feed or search_content.

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 the right context: use this tool when you need trending videos ranked by engagement within a time window. It does not provide explicit exclusions or alternatives, but the context is clear enough for an agent to choose between this and the listed siblings.

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