brc_update_purchase

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

Discloses the confirmation behavior and the need for explicit user confirmation, which is valuable. However, with no annotations, the description does not cover other behavioral traits such as permissions required, side effects, or idempotency.

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, front-loaded with the main action, and packs essential process details in a single sentence. However, a structured format could improve readability.

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?

For a tool with 15 parameters, low schema coverage, and no output schema, the description is incomplete. It focuses solely on the confirmation flow and does not explain what fields can be updated, the expected response, or error handling.

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?

With only 20% schema description coverage, the description adds meaning only for confirmWrite. The other 13 parameters lack explanation, leaving the agent unclear about their purpose beyond the schema's sparse 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 updates a BRC purchase and explains the two-step confirmation process. However, it does not differentiate this tool from sibling update tools, though the name already serves that purpose.

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 guidance on the two-call pattern with confirmWrite, including the important instruction that preflight is not confirmation. However, it does not advise when to use this tool versus creating a purchase.

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