tcg_collection_remove

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

Discloses soft-delete default (status->'sold') and hard-delete option. Pairing with sold fields is explained. Annotations already mark destructiveHint and idempotentHint, so description adds context on the soft/hard behavior beyond the annotations.

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?

Two sentences, no unnecessary words. First sentence states core behavior, second provides a contextual hint. Efficient 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?

Given the presence of an output schema, return value details are not needed. Description covers the main behavior, default mode, and optional disposition capture. Missing explicit mention of idempotency but that's covered by annotation. Reasonably complete for the tool's simplicity.

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 already describes some parameters (e.g., hard has a description). The description adds value by suggesting pairing sold_price and sold_date with the remove action. However, most parameter meaning is already in schema.

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?

Clearly states 'Remove a card' with the resource (card) and action (remove). Title in annotations adds 'Remove (or soft-delete)' which further clarifies. Distinguishes from sibling tools like tcg_collection_update or 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?

Implies usage for removing a card, and hints to pair with sold_price and sold_date for disposition. However, does not explicitly state when not to use it or compare with alternatives like tcg_collection_update or tcg_collection_attach_pricing.

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