index_nei_cx

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so safety is covered. The description adds the data source URL and the return type (pandas.DataFrame), which provides some context beyond annotations. However, it doesn't disclose potential rate limits, data coverage, or update frequency.

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 and structured as a docstring with source URL, return value, and return type. However, the first line repeats the annotation title exactly, which is redundant. The URL may be of limited use to an AI agent. Overall, it is efficient but not perfectly polished.

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 simple zero-parameter tool, the description provides the essential information: what data is returned and in what format. It lacks details about the data's structure or interpretation, but given the tool's simplicity and the presence of annotations, it is mostly complete. An output schema is absent, so the return type mention partially compensates.

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?

Since the tool has zero parameters and the schema is empty, there is no parameter semantics to explain. Per the baseline for 0 parameters, a score of 4 is appropriate. The description does not need to compensate for any schema gaps.

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 identifies the tool as providing the China New Economy Index (中国新经济指数) from Caixin, with the ':return:' field specifying the returned data. However, it lacks an explicit verb like 'fetch' or 'get', making it slightly less direct than ideal. The specific index name distinguishes it from sibling index tools.

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?

There is no guidance on when to use this tool versus alternatives. With many sibling index_*_cx tools, the description does not explain what makes this index unique or when it should be preferred. No exclusions or alternative tool mentions are provided.

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