get_item_price_history

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

With no annotations, the description must convey behavioral traits. It discloses that the tool is a read-only query returning daily prices over a 180-day window, but doesn't mention data freshness, error handling, or any access constraints.

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 but includes several examples that reinforce usage. The redundant 'Usefull for...' sentence and minor typo prevent a 5, but the structure is clear and front-loaded.

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?

The examples include comparing two items and asking for a specific future date (1 April 2025), which could mislead the agent into thinking the tool accepts multiple items or arbitrary date queries. The description doesn't clarify that only a single item is accepted or that data is limited to the previous 180 days relative to now.

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 input schema fully documents both parameters (itemName and gameMode) with descriptions, so the description doesn't need to add parameter semantics. The examples illustrate query phrasing but don't add new information about the parameters themselves.

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 states 'Returns the prices each day of a given item for the previous 180 days', which is a specific verb, resource, and time scope. It clearly differentiates from sibling tools like get_item_details or player-focused tools.

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 says it's 'useful for seeing price trends' and includes query examples covering single and comparative requests. It doesn't explicitly name alternatives or exclusions, but the context of siblings makes the intended use clear.

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