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

With no annotations, the description carries the full burden and does a fair job: it discloses per-call cost (0.011 USDC), that additional pages require separate requests, that null means unknown, that a summary/header is not the underlying record list, and it disclaims freshness/completeness/safety certification. What is missing is any auth/permission requirement or failure behavior, keeping it out of the top band.

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 well, but the body is a run-on of disclaimers that repeat the same idea — 'no ... completeness ... or safety certification' near the start and 'No completeness or safety guarantee' at the end. The repetition costs space without adding new information.

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 no-output-schema, no-annotation count tool, the description supplies pricing, pagination, null semantics and entity-identity caveats, which covers the operational essentials. It still never describes what the returned count(s) actually contain or how the risk categories are broken out, so an agent cannot fully predict the response.

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 0% and the single 'arguments' object is opaque (additionalProperties: true), so the description must compensate. It does point to get_cn_data_tool_schema('v3_business_risk_count') for the argument contract and names company_id as the entity key, which is meaningful, but it leaves the rest of the argument shape undocumented.

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 ('查询经营异常、行政处罚及风险总数') gives a specific verb and resource set — it is a count/aggregate over business-abnormality, administrative-penalty and related risk data. It partially distinguishes itself from siblings like cn_data_v3_administrative_penalty and cn_data_v3_operation_exception by being a total-count rather than a record list, though it never names those siblings directly.

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 only usage hint is 'Use company_id from cn_data_v3_company_detail', which tells where to source the key field but not when this tool should be chosen over the many risk-related siblings. There is no when-to-use or when-not-to-use guidance and no stated prerequisites.

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