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

With no annotations, the description carries the full burden and delivers real behavioral facts: cost (0.011000 USDC per single call), pagination behavior (additional pages require separate requests), null semantics (null = unknown), and the warning that a summary/header is not the underlying record list. These are substantive beyond a bare schema, though the repeated 'no completeness or safety guarantee' disclaimers add noise rather than information.

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 purpose is front-loaded in the first clause, which is good, but the English block piles on overlapping negative disclaimers (freshness/completeness/ownership/safety, then 'No completeness or safety guarantee' again). Several sentences restate the same caveat instead of earning their place.

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?

For a read-only count tool with no output schema and no annotations, the definition covers the practical essentials an agent needs: cost, pagination limits, null interpretation, and a pointer to both the argument schema tool and the company_id source. The remaining gap is the exact argument shape, which is deferred rather than missing.

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 0% and the single argument object is untyped (additionalProperties: true), so the description must compensate. It does partially by naming company_id, pointing to cn_data_v3_company_detail for its source, and delegating the full contract to get_cn_data_tool_schema("v3_media_count"), but the actual accepted fields are still not spelled out here.

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 Chinese lead sentence states a specific verb (查询/query) and resource (微信公众号、微博与新闻舆情数量 – WeChat, Weibo and news-opinion counts), so an agent understands it returns aggregate media-mention counts. It does not, however, differentiate itself from siblings like cn_data_v3_wechat, cn_data_v3_sina, or cn_data_v3_news_header, so it stays short of a 5.

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 steers parameter usage ("Use company_id from cn_data_v3_company_detail") and frames the tool as one selected Chinese company data call, which implies context. But it never states when to prefer this count tool over the sibling detail/list media tools, leaving the routing decision to inference.

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