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

No annotations are provided, so the description carries the full behavioral burden, and it does disclose several real traits: null values mean unknown, a summary/header is not the underlying record list, additional pages require separate requests (pagination), and per-call cost. It stops short of stating authorization or read-only status, and the legalistic boilerplate is vague.

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?

Purpose is front-loaded in the first sentence, but the remainder is a run-on chain of disclaimer fragments that repeats itself ('No independent entity identity, freshness, completeness...' and 'No completeness or safety guarantee' say nearly the same thing). Signal is diluted by boilerplate that could be a single disclaimer.

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?

With no output schema, the description should characterize returns, and it nominally does (taxpayer type, status, basic tax info) plus adds cost, pagination, and null semantics. For a single-company data lookup against an opaque argument object it is minimally adequate, though the actual field list and argument names remain undisclosed.

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 input schema is an opaque one-property object at 0% description coverage, so the schema provides essentially nothing. The description compensates by directing the agent to get_cn_data_tool_schema("v3_tax_basic") for the argument shape and by naming company_id as the key input, but it does not itself document the parameters.

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 Chinese sentence states a specific verb+resource: it queries taxpayer type, status, and basic tax information for one company. That is clear on its own, but the description never explicitly distinguishes this from sibling tax tools (cn_data_v3_tax_credit, cn_data_v3_tax_overdue, cn_data_v3_tax_punishment_list), so the agent must infer the split from the names.

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 access hint: use company_id from cn_data_v3_company_detail, which tells the agent where the required input comes from. However, it gives no when-to-use-vs-alternatives guidance against the other tax-related siblings, leaving selection to the agent's inference.

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