spot_hog_lean_price_soozhu

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds only the source URL and return type (pandas.DataFrame), without disclosing data update frequency, coverage scope, or other behavioral traits beyond what annotations imply.

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 extremely short, front-loading the resource name and source URL. It uses efficient docstring-like syntax, though it lacks a proper sentence structure and could be more readable.

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 read-only tool, the description provides the source and return type. However, it does not explain the DataFrame's exact contents (e.g., columns, date range, granularity) or explicitly differentiate it from closely related hog price tools like spot_hog_soozhu, leaving some ambiguity.

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, and schema description coverage is trivially 100%. With 0 params, the baseline is 4; the description adds no parameter information, but none is needed.

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 the specific data resource (全国瘦肉型肉猪) and source URL, making it clear this tool returns national lean hog price data. It distinguishes from sibling hog tools by the '瘦肉型' qualifier, but lacks an explicit verb like 'fetch' or 'get', relying on the tool name to imply retrieval.

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 the many similar sibling hog price tools (e.g., spot_hog_crossbred_soozhu, spot_hog_soozhu). There is no mention of alternatives or selection criteria, leaving the agent to infer the correct choice.

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