get_commodity_price

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

No annotations provided; description states 'live price' implying real-time data and lists acceptable commodities. Does not disclose additional behavioral traits such as rate limits, update frequency, or return structure.

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 concise sentences: first states purpose, second provides example. No extraneous information; every word is necessary.

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 simple tool with one enum-like parameter and no output schema, the description is complete. It specifies input values and implies output (live price) without needing elaboration.

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?

Only one parameter (commodity) with 0% schema coverage. The description lists all valid values (GOLD, SILVER, etc.) and provides an example, fully compensating for schema's lack of enum or description.

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 'Get live price for a commodity' and lists specific commodities (GOLD, SILVER, etc.), distinguishing it from sibling tools like get_all_commodity_prices or get_commodity_history.

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?

Provides an example call (get_commodity_price('GOLD')) demonstrating usage. Does not explicitly state when to use vs. alternatives, but the example and enumerated values guide correct invocation.

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