value_collection

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Refresh' implies mutation/persistence of stored values, but the description doesn't state whether it writes data, requires authentication, has rate limits, or is reversible. It also fails to clarify side effects on stored collection values.

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?

A single compact sentence with zero filler. It conveys the verb, resource, scope (matched variants), and output currencies efficiently. Excellent brevity with no wasted words.

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 having an output schema, this is a potentially mutating 'Refresh' action with no annotations and no usage guidance. The description is too terse to be complete: it doesn't explain what 'refresh' means operationally, what happens to prior stored values, whether it's a long-running operation, or how results are structured. Compared to the calibration example for mutation tools with gaps, this falls short of completeness.

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 tool has zero parameters with 100% schema coverage, so the baseline per rubric is 4. The description appropriately conveys that it operates on the entire collection (default scope) with no parameter detail needed. Nothing in the description contradicts or adds beyond the schema because there are no parameters to elaborate on.

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 uses a specific verb ('Refresh') tied to a resource ('value_collection'), describing price-variant totals in two currencies (TCGPlayer USD and CardMarket EUR). It distinguishes the action reasonably from siblings like summarize_card_value or get_card_prices, though it doesn't explicitly state what the collection refresh returns.

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?

No guidance is provided on when to use this tool versus alternatives. Given many price/value siblings (get_card_prices, summarize_card_value, get_collection_value-analogous tools, collection_summary), the description doesn't clarify whether this refreshes underlying price data or just computes saved values, leaving the agent to guess the appropriate use case.

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