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 adds one genuinely useful behavioral note: the returned content is user-generated and untrusted, which is a real safety signal. However, it omits scope (global vs. per-account), pagination, rate limits, and any return-shape hints, leaving significant behavioral gaps for a no-annotation tool.

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 short sentences with zero waste; the core capability is front-loaded and the trust caveat follows immediately.

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 and no annotations, the description should do more. It never establishes the scope of 'top' (which account, what time window) nor describes the returned media shape, so an agent cannot fully predict the result. The trust warning is a partial offset.

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 limit (1-100) and sort_by ('likes' or 'comments') are already fully documented in the schema. The description's 'by likes or comments' merely echoes sort_by without adding format or edge-case meaning. Baseline 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 ('Get top posts') plus the ranking dimension ('by likes or comments'). This distinguishes it from get_user_medias (an unfiltered listing) and get_top_tt_medias (the TikTok equivalent), though the description never explicitly names those siblings or clarifies whose posts are being ranked.

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?

There is no explicit when-to-use guidance, no prerequisites, and no routing to alternatives like get_user_medias or search_media_captions. The usage is only implied by the tool name and the sort_by option.

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