get_stash_value

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

With no annotations provided, the description carries the full burden and does so well: it explicitly says the operation reads public listings with no login, exposes the visibility limitation, explains the account configuration, and describes the refresh behavior versus returning the latest snapshot.

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 front-loaded with a one-sentence purpose, then adds tightly scoped implementation context. There is no fluff or repetition of schema fields; each sentence contributes necessary guidance.

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 output schema exists, so return-format explanation is unnecessary. The description covers authentication, data source, visibility, and refresh behavior, which is strong. However, the league parameter is left undocumented and no guidance is given on valid league values or how the valuation result is expressed, leaving a meaningful gap.

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 description explains the refresh parameter clearly but says nothing about league, which is one of only two parameters and has a default that is not meaningful without context. Since schema description coverage is 0%, the description needed to compensate for both parameters but only covered one.

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 opens with a specific verb and resource: "Value your own stash against collected prices." It clearly identifies the operation as reading an account's public listings, which separates it from siblings like search_items, get_price, or get_stash_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?

It gives clear context for when this tool is the correct path: the authenticated stash API is OAuth-only and closed, so public listings are the working approach. It also states the refresh-vs-snapshot decision. It does not explicitly name alternative sibling tools or say when not to use it.

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