China Department Statistics

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds behavioral traits like fetchAll being slow and indicator defaulting to first keyword, providing additional transparency beyond annotations.

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 structured with a header, parameter list, and department enumeration. It is concise and informative, though slightly longer due to the list, but every sentence adds value.

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?

The description lacks information about the output format or structure, which is important since no output schema is provided. It adequately covers input parameters and basic behavior but not the return data.

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 100%, so the baseline is high. The description adds context by listing valid department keys and explaining the behavior of optional parameters (indicator, fetchAll), which adds meaning beyond the schema.

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 queries department statistics from the National Bureau of Statistics, covering multiple fields. It uses a specific verb 'query' and identifies the resource, and the list of departments distinguishes it from sibling tools like ext_cn_census or ext_cn_department_list.

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 provides parameter usage details (optional indicator, default values, slow fetchAll) but does not explicitly state when to use this tool versus alternatives. It implies usage context but lacks direct comparisons.

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