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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description's read-only nature is already covered. The description adds value by disclosing the default time window (one week), the cost of 2 credits per call, and the return structure (breakdown by content types and creators), which are not present in annotations or schema.

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 four terse sentences covering purpose, filtering, usage workflow, and cost. Every sentence carries useful information without redundancy, and the main purpose is front-loaded in the first sentence.

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 tool's read-only, idempotent nature (from annotations), optional parameters, and lack of output schema, the description sufficiently covers the return breakdown, default behavior, cost, and typical usage scenario. It could be slightly clearer about what 'overperforming' means and how limit applies, but overall it is comprehensive enough for an agent to select and invoke the tool effectively.

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 50% (query and timeFrame are described; limit and platforms are not). The description adds meaning for platforms by mentioning 'Filter by keyword and platform' and confirms the default window for timeFrame, but it does not explain the 'limit' parameter's semantics or interaction with the result set. This is partial compensation but leaves a gap for limit.

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 ('Returns') and resource ('top overperforming posts in a niche'), and further specifies the output includes a breakdown by content type and creators. This clearly distinguishes it from sibling tools like 'get_trending_outliers' or 'search_outliers' by focusing on niche-level trends rather than generic outliers or profile comparisons.

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 explicitly positions the tool as 'Great as the first call in a content-research loop' and suggests follow-ups like deep-diving or remixing winners, providing clear contextual guidance. It does not name alternatives or state explicit exclusions, but the usage context is unambiguous and helpful.

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