brc_delete_prepayment

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

No annotations are present, so the description carries the full burden. It discloses the need for user confirmation via confirmWrite and the prerequisite of getting a timestamp. However, it does not mention irreversibility, side effects, or required permissions.

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?

Three sentences, each essential. Front-loaded with the main action, followed by key constraint and workflow step. No fluff.

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 and no annotations, the description covers the essential aspects: purpose, prerequisites, parameter hints, and usage guardrails. It is adequate for a simple delete tool, though it could mention return values 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 coverage is 100%, so parameters are described. The description adds value by specifying the timestamp format (Base64) and the workflow hint to retrieve it via brc_get_prepayment. It also reinforces the confirmWrite behavior.

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 states 'Removes an existing parent Prepayment by id.' This is a clear verb+resource pair that distinguishes the tool from its siblings, such as brc_create_prepayment and brc_update_prepayment.

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 prerequisites: requires the prepayment timestamp in Base64 format, advises to use brc_get_prepayment first, and warns not to set confirmWrite=true until user confirms deletion. This offers clear when-to-use and when-not-to-use guidance.

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