brc_delete_accrual

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

Discloses deletion (destructive) and confirmation workflow. No annotations exist, so description carries burden. Could elaborate on permanence or side effects, but core behavioral trait is covered.

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 purposeful: purpose, prerequisite/warning, confirmation constraint. No redundant 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 4 parameters, full schema coverage, and no output schema, description covers key points: prerequisite action, confirmation logic. Slight gap on whether deletion is reversible, but adequate for the tool's function.

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?

Adds context beyond schema: timestamp must be Base64 from get_accrual (with example), confirmWrite usage warning. All 4 parameters are explained in schema, and description enriches meaning.

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 verb 'Removes' and the resource 'existing parent Accrual by id,' distinguishing it from other accrual tools (create, get, update, list). The name also reinforces the deletion action.

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 to retrieve the timestamp and warns against setting confirmWrite=true without explicit user confirmation. Could add when not to use, but current guidance is clear.

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