brc_create_customer

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

With no annotations, the description fully discloses key behaviors: does not handle opening balance transactions, performs email-name mismatch checks, and requires a two-step confirmWrite workflow. Lacks details on success/error responses but covers critical behavioral traits.

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 a single paragraph that covers multiple points. It is front-loaded with the primary action but could be more structured (e.g., bullet points) for clarity. Not overly verbose but could be tighter.

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?

Describes key workflow and edge cases but omits details about the payload structure (though schema says 'raw BRC payload') and return values. Given no output schema, description should include what the tool returns or error conditions.

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 covers 100% of parameters, but the description adds significant context: explains the confirmWrite workflow, warning about opening balances, and email-check logic. This goes beyond the basic schema descriptions.

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 it creates a BRC customer using a raw BRC payload. It distinguishes from sibling create tools by specifying 'customer' and detailing unique behaviors like handling opening balances and email checks.

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 clear when-to-use context and explicit workflow instructions (e.g., not to set confirmWrite on first call, warn about opening balances and email mismatches). However, does not explicitly state when not to use this tool or alternative tools for other entities.

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