brc_create_product

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

Transparently describes the two-step confirmation process (preflight then confirm). No annotations exist, but the description covers the key behavioral aspect, though it could mention success/failure responses.

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, front-loaded with purpose, then detailed instructions. The second sentence is long but packs important procedural info efficiently.

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?

Covers the preflight flow well, but lacks details on return values beyond 'confirmation_required and payload preview'. With no output schema, some return info would be helpful.

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 description coverage is 100%, and the description adds crucial context for confirmWrite, explaining its toggling based on user confirmation. This goes beyond the schema's description.

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 creates a BRC product using a raw BRC payload, distinguishing it from sibling tools like brc_batch_products and brc_update_product.

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?

Provides explicit step-by-step instructions: first call without confirmWrite: true, show preview to user, then retry with confirmWrite: true only after explicit confirmation. Warns that passing preflight is not confirmation.

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