macro_china_lpi_index

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds a source URL and return type, but no behavioral context such as rate limits, data coverage, or potential performance implications. It adds minimal value beyond what annotations already provide.

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 (only a title, URL, and return type), so it is concise. However, it is not well-structured; the docstring format mixing a URL with :return: and :rtype: is awkward, and the title is redundant. It is under-specified rather than merely concise.

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 tool has no output schema and the description provides minimal context: it names the index, gives a source URL, and states the return type. It does not explain what data is actually returned (e.g., columns, time period, frequency) or how this index relates to other macro indicators. For an agent, this is insufficient on its own to fully understand the tool's output.

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 is trivially complete (100% coverage). The description adds no parameter semantics, but with no parameters this is not a gap; a baseline score of 4 is appropriate.

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 is essentially '物流景气指数' (logistics prosperity index), which is just the title. It includes a URL and return type docstring, but lacks an explicit verb like 'get' or 'query'. It restates the tool's name rather than clearly describing its function, and does not distinguish it from sibling macro indicators.

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 (e.g., other macro indicators like macro_china_pmi). No context, prerequisites, or exclusions are provided, so the agent gets no help in selecting this tool over siblings.

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