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

With no annotations, the description carries the full behavioral burden and does add some value: null means unknown, a summary/header is not the underlying record list, and there is no completeness/safety guarantee. It omits any recovery/rate behavior beyond pricing, so it is adequate but incomplete.

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, but the text repeats itself: "No independent entity identity, freshness, completeness ... or safety certification" and again "No completeness or safety guarantee." That redundancy and the mixed-language boilerplate are not 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 1-param, no-output-schema, no-annotation tool the description does cover pricing, pagination, null semantics, and the origin of company_id. But the deferred schema resolution and the opaque arguments object leave the agent without enough to construct a call confidently.

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 parameter is an opaque nested object with additionalProperties=true. The description only hints at company_id and otherwise defers to get_cn_data_tool_schema("v3_recruit_count") rather than documenting the actual arguments, so it does not compensate for the coverage gap.

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 line "查询企业招聘岗位数量与概览" states a specific verb (query/count) and resource (company recruitment positions), making it distinguishable from list/detail siblings like cn_data_v3_work_list. It is clear but does not explicitly contrast itself with the other *_count siblings, so it stops 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?

It gives one actionable prerequisite: "Use company_id from cn_data_v3_company_detail." It also notes that additional pages require separate requests. However, it offers no when-to-use/when-not guidance against the many competing count siblings (certificate_count, bid_count, etc.).

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