get_commodity_history

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states the tool retrieves historical price data and lists periods, but fails to mention read-only nature, data source, output structure, or any rate limits, leaving significant gaps.

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?

Description is three sentences: purpose, parameter details, and example. No unnecessary words, front-loaded with purpose.

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 should explain the return format (e.g., array of objects with date, price, etc.). It does not, leaving the agent uninformed about what data to expect. Additionally, no prerequisites or limitations are noted.

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 0%, so the description must add meaning. It lists valid period values and gives an example showing commodity format, but does not explain what each period means or describe the commodity parameter's expected format beyond the example.

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 tool name 'get_commodity_history' combined with the description 'Get historical price data for a commodity' clearly states the action and resource, distinguishing it from siblings like 'get_commodity_price' and 'get_all_commodity_prices'.

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 lists valid periods and provides an example, implying usage for historical data. However, it does not explicitly state when to use this tool versus alternatives like 'get_commodity_price' for current prices, leaving the agent to infer.

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