macro_euro_unemployment_rate_mom

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

The description adds the data range (19980501 to present), the return type (pandas.Series), and the return value semantics (今值, current value in %), which supplements the annotations' read-only/idempotent safety profile. It also provides source URLs, giving additional context about data origin. No contradiction with annotations.

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 front-loaded with the core purpose, followed by source URLs and return type. It is compact and easy to parse, though the URLs contribute minor noise for an agent's decision-making.

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 simple no-parameter retrieval tool with good annotations, the description provides sufficient context: the data range, the metric (current value in %), the return type, and source links. It is complete enough for an agent to invoke the tool without further clarification.

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 fully covers the input space. The description doesn't need to explain parameters; baseline for 0 params is 4.

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 tool as a Eurozone unemployment rate report with a data range from 19980501 to the present, and the return line specifies the current value in percentage. It distinguishes from other region-specific unemployment rate tools via '欧元区' (Eurozone), though it doesn't explicitly elaborate on the 'mom' suffix in the description, leaving minor ambiguity.

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 other macro unemployment rate tools or the numerous sibling macro_euro tools. The description only provides a data source and return type, with no exclusions or alternative recommendations.

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