brc_delete_accrual

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

Without annotations, the description bears full burden. It discloses the destructive nature, required timestamp format, and confirmation step. However, it omits information about side effects, irreversibility, or response behavior.

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 concise sentences. The main action is front-loaded, with critical usage instructions following. 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?

For a delete tool with no output schema and no annotations, the description lacks return value information and error conditions. It provides key prerequisites and safety steps but not a complete operational picture.

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 descriptions cover all 4 parameters. The description adds context: timestamp must be retrieved from brc_get_accrual and confirmWrite should only be true after user confirmation. This exceeds what schema provides.

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 action (removes) and the specific resource (existing parent Accrual by id). It distinguishes itself from sibling delete tools by specifying the resource and mentioning the prerequisite timestamp retrieval.

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?

Explicitly instructs to use brc_get_accrual first and warns not to set confirmWrite=true without explicit user confirmation. However, it does not mention when not to use the tool or compare to other deletion-related tools.

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