macro_china_mobile_number

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds the return type (pandas.DataFrame) and the data source URL, which are useful but do not disclose additional behavior like error handling, rate limits, or data range. No contradiction with 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 very short, but it includes a long URL that is not essential to understanding the tool's function. The structure is docstring-like with ':return:' and ':rtype:', which is organized but somewhat under-specified. It earns a middle score for brevity but lacks polish.

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 parameters and no output schema, the description only reiterates the topic and gives a URL. It does not explain the data's time range, granularity, or columns, which could leave the agent uncertain about what the DataFrame contains. The simplicity of the tool raises the bar for clarity, but the description remains minimal.

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 tool has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it correctly remains silent on this aspect.

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 says '手机出货量' (mobile phone shipments) and specifies the return type, but it lacks an explicit verb like 'get' or 'return'. It identifies the resource but is essentially a label with a data source URL, not a clear statement of function. It is distinguishable from siblings by its unique topic, but the purpose is only implicitly conveyed.

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 no guidance on when to use this tool versus alternatives. It does not mention context, prerequisites, or exclusions. Among many macro_china_* siblings, there is no situational differentiation.

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