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

With no annotations, the description carries the full burden and does disclose real traits: pagination ('additional pages require separate requests'), null semantics ('null values mean unknown'), cost (0.011 USDC per call), and the caveat that a summary/header is not the underlying record list. The repeated 'no certification/guarantee' disclaimers are boilerplate rather than specific, but the pagination, null and cost disclosures are genuinely useful.

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 is front-loaded and the operational notes are short, but the text is padded with redundant disclaimers ('No ... completeness ... certification' and 'No completeness or safety guarantee' state the same thing twice) plus mixed-language content that adds noise.

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 single-purpose count tool with no output schema and an opaque argument object, the description covers what is returned (risk counts / summary), pagination, cost, and the input source. The main remaining gap is that the argument fields themselves are delegated to another schema tool rather than described here.

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?

The schema is a single untyped 'arguments' object with additionalProperties=true and 0% description coverage, so the schema explains nothing. The description partially compensates by naming company_id and pointing to get_cn_data_tool_schema for the full argument contract, but it does not document the actual arguments inline.

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 opening sentence names a specific verb+resource ('查询...司法风险计数') and enumerates the covered categories (失信、被执行、限高、裁判文书), which lets an agent distinguish it from near-neighbors like cn_data_v3_business_risk_count. It is clear, though the Chinese-only purpose statement plus trailing boilerplate slightly muddies front-loading.

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?

It gives a concrete prerequisite ('Use company_id from cn_data_v3_company_detail') and directs the agent to get_cn_data_tool_schema("v3_judicial_count") for argument shape, which is useful routing. It never states when to prefer this count over a sibling or when not to use it, so usage guidance stays implied.

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