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

Beyond the read-only/idempotent annotations, the description discloses meaningful behavior: the database is continuously crawled, results may include deleted posts and deactivated accounts, stats are frozen at deletion, and each call costs 1 credit. No contradiction with the annotations exists.

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 dense and front-loaded with the essential ranking concept, and every sentence carries useful information. The long enumerative sentence is justified by the large parameter set, though it is slightly harder to scan than a more structured layout would be.

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 absence of an output schema and the 17-parameter surface, the description explains return contents (metadata, stats, thumbnails) and important edge cases (deleted posts, deactivated profiles, cost). Missing details like pagination and watchlist scoping are minor but prevent a perfect score.

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?

With only 18% schema description coverage, the description compensates by enumerating the filter dimensions (platform, keyword, exact handle, content type, outlier-score band, view band, follower band, engagement-rate band, time window) and sort options. It does not define units for numeric bands or mention page/pageSize/watchlistId semantics, so it is not fully complete.

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 clearly names the resource ('continuously-crawled database of social media posts') and the core verb ('Search...ranked by outlier score'), making the purpose specific and unambiguous. It does not explicitly contrast itself with siblings like get_trending_outliers, but the filter/search framing sufficiently distinguishes it from profile-oriented tools.

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 gives an explicit use context: 'Use this to find proven viral formats in any niche before creating content.' It also advises filtering out deleted/deactivated posts when only live content is wanted. It does not, however, name alternatives or state when not to use this tool.

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