veroq_commodities

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

No annotations are provided, so the description carries the burden. It discloses the cost (2 credits) and return fields (price, change, change percent, unit). However, it does not mention authentication requirements, rate limits, or data freshness, leaving some behavioral 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?

The description is concise (4 sentences plus labeled sections) and well-structured with WHEN, RETURNS, COST, EXAMPLE. It front-loads the key purpose but could be slightly more compact.

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?

Given the tool's simplicity (single optional parameter, no output schema, one sibling set), the description fully covers usage, return values, cost, and an example. No additional context is needed.

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 sole parameter 'symbol' is already fully described in the input schema with examples. The description reiterates this info without adding new semantic meaning, so baseline score of 3 is appropriate for high schema coverage.

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 it retrieves commodity prices for a list of specific commodities (gold, silver, oil, etc.) and distinguishes behavior between no argument (returns all) and passing a slug (single commodity). This differentiates it from sibling tools like 'veroq_crypto' or 'veroq_forex'.

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 'WHEN TO USE' section explicitly states the tool is for commodity market data covering precious metals, energy, and industrial commodities. While it does not list exclusions or direct alternatives, the context is clear enough for an agent to decide.

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