get_commodity_price

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

With no annotations, the description carries the full burden but only states it returns min, max, and modal prices from today's data. It does not disclose behavior if data is missing, freshness guarantees, or any rate limits. This gap leaves the agent uncertain about edge cases.

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?

Two short, front-loaded sentences that efficiently communicate the tool's purpose and output. No waste.

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?

Despite an output schema existence, the description lacks explanation of optional parameters and behavioral details. Given 4 parameters and no annotations, the description is insufficiently complete for agents to reliably invoke the tool.

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 description coverage is 0%, yet the description only refers to a 'specific commodity' without explaining the state, district, or market parameters. The required commodity parameter lacks format or example, failing to add value beyond the schema.

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 retrieves current daily wholesale prices for a specific commodity, specifying returns of min, max, and modal prices from Agmarknet data. It distinguishes itself from sibling tools like compare_markets or list_commodities by focusing on price retrieval for a single commodity.

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 implies usage for getting commodity prices but does not provide explicit guidance on when to use this tool versus alternatives like compare_markets or get_price_summary. No exclusions or conditions are mentioned.

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