brc_delete_sales_invoice

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

With no annotations, the description fully covers the two-step confirmation behavior. It discloses that the first call returns a confirmation_required response and a payload preview. However, it does not mention the irreversible nature of deletion or what happens after successful confirmation.

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 extremely concise: two sentences that front-load the core action and immediately follow with critical usage guidance. No unnecessary words.

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 no output schema, the description provides essential context about the confirmation flow. It mentions the return of confirmation_required and a payload preview but does not detail the preview structure or final success response. This is adequate for a delete tool but could be slightly richer.

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 75% (3 out of 4 parameters described). The description adds no additional meaning for id, companyName, or confirmWrite beyond what the schema already provides. It does not address the confirmDelete parameter at all, leaving its purpose unclear.

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?

Description clearly states it deletes a BRC sales invoice by id using timestamp confirmation. The verb 'deletes' and specific resource 'sales invoice' make the purpose unambiguous, and it stands out among sibling delete tools by mentioning the two-step confirmation process.

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?

Explicit instructions are provided: first call without confirmWrite returns confirmation_required and a payload preview, then retry with confirmWrite only after explicit user confirmation. It also clarifies that passing preflight is not confirmation, which prevents misuse.

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