cn402_geo_cn_province

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

No annotations are provided, so the description carries the full burden. It mentions lookup by name or code and lists return fields, but does not disclose behavior when no parameters are given, error handling, or whether both parameters can be used together. It also includes an ambiguous pricing line that adds no functional clarity.

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 verbose with repetitive keywords in multiple languages (e.g., 'China province lookup', '中国省份查询'). The pricing note ('Price: unknown on Base...') is extraneous and potentially confusing, detracting from conciseness.

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 two optional parameters and no annotations, the description should clarify default behavior (e.g., if no parameters are provided), output structure, and error conditions. It only partially describes the return fields but omits how results are returned (single vs. multiple provinces) and lacks any output schema or cross-reference to sibling tools.

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 100% with descriptions for both parameters. The description adds value by enumerating the returned fields (capital, area, population, region), which aids understanding beyond the parameter names and basic schema descriptions.

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 it looks up China province information by name or code, and lists the fields (name, capital, area, population, region). It distinguishes from the sibling tool cn402_geo_cn_city by focusing on provinces.

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 does not provide guidance on when to use this tool versus alternatives, such as cn402_geo_cn_city for cities. It also fails to mention prerequisites or exclusions (e.g., only mainland China provinces).

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