policy_bigdata_approved_project_stats

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

No annotations are provided, so the description must bear full burden. It does not disclose whether the tool is read-only, any side effects, required permissions, rate limits, or error behavior. It only hints at output content but lacks explicit behavioral traits.

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 description is concise, front-loading the purpose, then listing parameters with brief explanations. Every sentence contributes; no fluff. It could be slightly more structured, but it's efficient.

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?

Given no output schema, the description partially compensates by listing the types of information returned (levels, authorities, subsidies, trends). However, it does not provide a detailed output structure or example, leaving some ambiguity about the exact format.

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%, but the description adds value by explaining the possible values for matchKeyword (name, registration number, etc.) and keywordType, and suggests using enterprise_get_keyword_search if full name is not available. This goes beyond the schema definitions.

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 description clearly states the tool's purpose: query enterprise approved policy project statistics, covering levels, authorities, subsidies, and trends. It uses a specific verb ('查询') and resource ('获批政策项目统计'), and is distinguishable from sibling tools like policy_bigdata_policy_info and policy_bigdata_policy_search.

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 implies usage for understanding enterprise-approved policy projects but does not explicitly state when to use this tool vs alternatives. No when-not or alternative recommendations are provided; usage is implied from the purpose.

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