macro_china_bdti_index

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false) and idempotency. The description adds the source URL and return type (pandas.DataFrame), which are useful behavioral traits, but it does not explain data granularity, time span, or any underlying data retrieval behavior.

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 and front-loaded, but the first line redundantly repeats the title from annotations. The URL and return type provide value, yet the duplication constitutes minor waste, making it adequate but not exemplary.

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?

Even though the tool is simple with no parameters, the description does not clarify what the returned DataFrame contains (e.g., historical index values, dates, columns), what time range or frequency is covered, or what the BDTI index conceptually represents. The URL hints at East Money but leaves the output contents ambiguous.

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 input schema has zero parameters, so the description is not responsible for explaining parameters. The baseline of 4 applies, and no additional parameter semantics are needed.

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 merely states '原油运输指数' (crude oil transport index), which is identical to the title, along with a source URL and return type. It does not articulate a distinct action or resource beyond the tool's name, and it fails to differentiate from similar macro indices like macro_china_energy_index or macro_china_freight_index.

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. The description lacks any mention of use cases, prerequisites, or comparison with sibling tools.

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