tcg_collection_add_sealed

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

The description discloses that sealed product shares the same table as singles with a different product_type, and that one row is inserted per quantity unit for cost basis tracking. It also states the return format (list of card_ids). This adds value beyond the annotations, which only indicate non-read-only status.

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, with three sentences that front-load the main purpose. The second and third sentences provide necessary context without fluff. Every sentence earns its place.

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 description adequately covers the essential behaviors for adding sealed product, including internal storage and return values. However, it does not elaborate on error conditions or prerequisites (e.g., set existence), but these are common and the schema covers required fields.

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 already contains descriptions for most parameters (e.g., acquisition_price: 'Per-unit price'). The tool description adds no new parameter-specific information beyond the schema. Given the schema's existing coverage, a baseline score of 3 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?

The description clearly states the tool records sealed product as owned, and explains the internal storage distinction from singles. This directly addresses the purpose and differentiates from sibling tools like tcg_collection_add_card.

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 implies use for sealed products but does not explicitly state when to use this tool versus alternatives. It provides context but lacks clear when-not guidance or explicit reference to siblings.

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