Top posts about any topic, brand or product

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

Annotations cover open-world/idempotency but not cost, and the description adds real behavioral context: 'About one credit per platform searched', each `queries` variant is a paid call, and 'repeats inside 20 minutes are free'. It also states the ranking (by views). It stops short of describing pagination or result shape, so a 4 rather than 5.

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 core purpose and scope are front-loaded, and every clause carries routing, cost, or return-value information. It is a dense single paragraph, but with little genuine filler; the density borders on overloaded rather than wasteful.

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, the description still tells the agent what comes back (posts ranked by views) and covers cost, scope, and alternatives. It leaves result shape and pagination unspecified, a minor gap for a search tool with all params already documented.

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 100%, so baseline is 3, but the description adds meaning to `queries` (adds 'best X' / 'X review' / #tag variants, each a paid call) and clarifies that the default is one query per platform across all three platforms. This enriches the schema rather than restating it.

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 (post search) and resource (posts about a subject) with concrete scope: organic TikTok, Instagram Reels and YouTube in one call, ranked by views. It explicitly differentiates from siblings by saying it is 'Not the brand's own ads (search_meta_ads / research_ads) and not the people (find_creators)', so an agent can route without opening a 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?

Gives explicit when-to-use conditions ('see what is actually being posted and watched about a subject', 'find clips worth cloning', 'read the hooks and angles an audience already responds to') and names the adjacent tools it is not (search_meta_ads, research_ads, find_creators). Nothing about selection is left to inference.

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