taiwan_farm_price

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

No annotations provided, so the description bears full burden. It discloses the tool returns price and volume data, covers specific categories, excludes others, and cites the data source. It does not mention side effects, but as a read-only query, that is acceptable. Adds useful context beyond schema.

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 concise: two sentences and a data source line. Front-loaded with purpose and output, followed by context and coverage. Every sentence adds value without redundancy.

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?

Without an output schema, the description adequately explains return values (price stats and volume), units, data source, and coverage. It misses details like handling multiple markets or error conditions, but is sufficient for common usage.

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?

Schema coverage is 100% with descriptions for both parameters (crop and market, with default). The description adds no new parameter-specific meaning beyond the schema; it re-iterates crop name examples and default market. Baseline 3 is appropriate.

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 states the tool queries latest wholesale market prices for agricultural products, with specific output (average, high, low price per kg, volume). It delineates coverage (vegetables, fruits, flowers) and exclusions (poultry, eggs, meat), distinguishing it from sibling tools focused on companies, real estate, or drugs.

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?

While the description does not explicitly contrast with alternatives, its domain (agricultural prices) is distinct from all sibling tools, making usage context clear. It implies use when needing Taiwan farm prices, especially during typhoon season, without specifying when not to use.

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