语料商店（局外成长）

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

With no annotations provided, the description carries the disclosure burden. It reveals that purchases spend accumulated corpus, items carry into the next run, and buying is disabled mid-run. It does not mention irreversibility or authorization, but these are implied by the game context and the explicit cost language.

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 dense but efficient, packing item catalog, pricing, workflow, and restrictions into a few clauses. Every element earns its place; there is no filler or repetition of schema content.

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 one optional parameter and no output schema, the description covers the essential aspects: purpose, item selection, cost, persistency, and the critical timing restriction. It does not detail output format or error handling, but the 'view goods and balance' phrase provides sufficient clarity for this simple use case.

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?

Schema coverage is 100% with one well-described 'buy' parameter. The description adds meaningful value by enumerating item IDs (mem, body, origin variants) with prices and clarifying that omitting the parameter triggers view mode. This goes beyond the schema's generic example.

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 this is a shop tool for browsing and purchasing persistent items with corpus currency. It distinguishes itself from sibling tools by specifying its role as the pre-run purchase step before tokenlife_start, listing exact item IDs and prices.

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?

Explicitly says to use before starting a run ('买完再 tokenlife_start 开局') and forbids buying during a run ('一世进行中只能看不能买'). It does not explicitly name alternative tools to avoid, but the workflow context is clear and actionable.

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