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

Annotations already declare readOnlyHint and openWorldHint, covering the safety profile. The description adds only the cursor-based pagination behavior, which largely overlaps the documented cursor parameter, and says nothing about rate limits, auth, or result ordering. It adds modest value beyond structured fields, fitting a 3.

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 written sentences with the core purpose front-loaded and the prerequisite routing placed second. Every clause earns its place with no redundancy.

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 an output schema present, the description need not explain return values, and annotations cover the safety profile. It supplies the essential prerequisite and pagination context, leaving only minor gaps such as result ordering or volume expectations for an open-world feed.

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 both parameters (id and cursor) are already fully documented, including an example for id. The description's mention of 'hashtag id' and 'cursor-based pagination' maps to these params but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 and resource ('Returns the videos listed for a TikTok hashtag id') and explicitly names the sibling tiktok_challenge for the related but distinct task of fetching hashtag details. An agent can distinguish this listing tool from the hashtag-detail tool without opening either 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?

The second sentence gives clear prerequisite context ('Use tiktok_challenge to retrieve TikTok hashtag details'), telling the agent where the required id comes from. It stops short of stating when to prefer this over other video-listing siblings (e.g., tiktok_posts, tiktok_search) or any exclusions, so it is clear context without full when/when-not guidance.

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