index_neei_cx

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

Annotations already convey read-only, idempotent, open-world behavior. The description adds the source URL and return type (DataFrame), which is useful but does not go further into data scope, update frequency, or other behavioral traits. It does not contradict annotations and adds minimal context beyond them.

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 extremely concise, containing only the source title, URL, and return type. Every line serves a purpose with no redundancy or filler. The structure is linear and front-loaded, placing the identifying title first.

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 zero-parameter tool, the description provides the essential return type (DataFrame) but lacks details about the dataset's columns, time range, or whether it is a time series or single snapshot. Without an output schema, such information would help, but the description is minimally sufficient for basic usage.

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 schema coverage is trivially 100%. The description has no parameter information to add, and none is needed. Baseline for 0 parameters is 4, and no deduction applies.

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 resource (新动能指数 / New Kinetic Energy Index) and states it returns a pandas DataFrame. The verb is implicit (get/fetch) but the ':return:' line makes the purpose evident. It distinguishes from similar index_*_cx tools by naming the specific index, though it does not explicitly contrast with siblings.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention scenarios, exclusions, or relationships to similar index tools like index_nei_cx or index_bei_cx. The description only implies usage through its title and return type, with no explicit context.

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