macro_usa_non_farm

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds useful context such as the data range starting from 19700102, the source URL, and the return type as pandas.Series, but does not elaborate on data structure, units, or update frequency.

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 brief and includes the key details (title, data range, source URL, return type). However, the phrase '美国非农就业人数报告' is repeated three times, adding redundancy without increasing information value.

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?

With no output schema, the description should explain what the returned pandas.Series contains. It provides the indicator name and data range, but lacks specifics such as the index format (e.g., dates), units (e.g., thousands), and whether the series is monthly or annual. This leaves some ambiguity for an agent interpreting the result.

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 fully covered and no parameter documentation is needed. The description correctly implies that no input is required, earning the baseline score of 4 for parameter semantics.

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 providing the US non-farm payroll report, with a specific title and data range. It distinguishes from sibling tools like macro_usa_adp_employment and macro_usa_unemployment_rate by naming the exact indicator. However, it lacks an explicit action verb like 'get' or 'retrieve', relying on the tool name to convey the retrieval purpose.

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?

No guidance is provided on when to use this tool versus related US macro indicators. The description does not mention alternatives or exclusions, leaving the agent to infer appropriate usage from the tool name alone.

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