macro_china_national_tax_receipts

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

Annotations already convey readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the source URL and indicates the return type, which provides some context beyond annotations. However, it does not disclose behavioral traits such as data freshness, time coverage, or any filtering/limitations.

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 compact, consisting of a one-line title, a source URL, and two short docstring lines specifying return value and type. Every element adds useful information without unnecessary verbosity.

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 is the only source of information about the returned DataFrame. It merely states 'national tax revenue' and the type, without specifying columns, time range, frequency, or data source details beyond a bare URL. This is insufficient for an agent to fully understand what data it will receive.

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 input schema has zero parameters, so there is no parameter semantics to clarify. Per the rubric, the baseline for a zero-parameter tool is 4, and the description does not need to compensate for missing parameter documentation.

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 resource as 'China - National tax revenue' and states that it returns a pandas DataFrame of this data, adding the source URL. Although it lacks an explicit verb like 'retrieve' or 'list', the intent is unambiguous. It does not differentiate from sibling tools beyond the name, but the resource and return type are specific.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or alternative tools for related data (e.g., other macro_china_* tools). This absence leaves the agent without decision support for tool selection.

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