获取全球PMI合成指数

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

With no annotations, the description carries the disclosure burden. It discloses the composite methodology and that per-economy detail is appended, which are meaningful behavioral traits. It does not mention update cadence or data source caveats, but the tool is a simple read-only-style data query and the output schema covers return structure.

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 a single concise sentence that front-loads the key formula, the output detail, and the intended use. Every clause adds information and there is no filler.

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 only one optional parameter, is covered by an output schema, and has no nested objects. The description provides the composite definition, the weighting formula, per-economy detail, and usage context, which is sufficient for an agent to select and call it correctly; only minor source/frequency details are absent.

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?

Schema description coverage is 100% and the only parameter, limit, is already described as '返回月数' with a default of 24. The tool description adds no additional meaning beyond the schema, so the baseline of 3 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 states a specific resource (the composite global manufacturing PMI index), gives the exact weighting formula (US ISM ×0.6 + Eurozone ×0.4), and notes it includes per-economy detail. This is a concrete, non-tautological statement that distinguishes global_pmi from similar macro/PMI siblings like macro_pmi.

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 phrase 'front-end international Tab' gives a UI context that implies global/international PMI queries, but the description does not explicitly state when to prefer this tool over sibling PMI or macro tools, nor does it name excluded alternatives.

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