get_market_sell_value

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

The description fully discloses the tool's behavior: matching cards, picking best offers with quantity caps, grouping by vendor, and returning totals. It also notes the authentication requirement. No annotations are provided, so the description carries the full burden, and it does so thoroughly.

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 fairly concise, covering the tool's purpose, process, and output in a single sentence. It could be slightly more structured by splitting into shorter sentences, but it contains no filler and is front-loaded with the primary action.

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 tool with no parameters and no output schema, the description is complete: it explains what the tool does, what it returns (vendor groups with per-item payouts and totals), and the requirement for an API key. No additional information 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 input schema has zero parameters, so the description does not need to add parameter details. Per the guidelines, zero parameters results in a baseline of 4. The description provides no extra parameter info, which is appropriate.

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?

Description clearly states the tool computes the market sell value of the user's entire inventory, detailing the process of matching cards to buylist offers and grouping by vendor. This specific verb-resource combination distinguishes it from sibling tools like get_card_buylist or get_portfolio_summary.

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 explains that the tool requires an API key, implying authentication context. It clearly states what the tool does, making it suitable for calculating total sell value, but it does not explicitly mention when not to use it or suggest alternatives.

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