bw_delete

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

Without annotations, the description discloses deletion is permanent and immediate, no activation needed, and includes a lock/unlock requirement. Does not cover all side effects but addresses a key dependency.

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: purpose with examples, process sequence, and dependency note. 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 2 parameters and no output schema, the description covers purpose, procedure, and a critical order constraint. Missing error handling details but sufficient for correct invocation.

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% and descriptions are adequate. The description adds examples (adso, iobj, trfn, dtpa) and format hints for object_name, going beyond the schema.

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 deletes a BW object permanently, lists examples (aDSO, InfoObject, etc.), and distinguishes from sibling tools like bw_delete_transformation_routine by being general.

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 sequence (lock, delete, unlock) and a dependency warning (delete aDSOs before InfoObjects). Does not explicitly compare to alternatives but context from siblings implies general vs specific use.

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