macro_euro_ppi_mom

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context the annotations do not: the data coverage window (19810301-present) and the return payload (今值 %, a pandas.Series). It omits update frequency and any rate-limit/auth notes, so it is adequate but not rich.

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 resource and date range are front-loaded, which is good, but the body embeds two raw source URLs and Sphinx-style :return:/:rtype: tags that read as scraped docstrings rather than agent-facing guidance. It is compact but not cleanly structured.

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 no-parameter data-fetch tool with no output schema, the description supplies the key facts an agent needs: what series it is, its historical span, and the return type/value. Missing only freshness/frequency details, which are secondary.

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 takes zero parameters (schema coverage 100%), so there is nothing for the description to disambiguate; per the baseline for a 0-param tool, this scores 4. The description correctly implies the tool is callable with no arguments.

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 names a specific resource (欧元区PPI月率报告 = Eurozone PPI MoM report) and pins its scope (data range 19810301-present), which is enough for an agent to identify it. It does not, however, explicitly distinguish itself from the many sibling macro_euro_* and macro_*_ppi tools, so differentiation relies on the name alone.

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 statement of when to use this tool versus alternatives such as macro_china_ppi_yearly or macro_usa_ppi, nor any prerequisites or exclusion conditions. The agent must infer usage purely from the resource name.

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