abap_bopf_delete

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

Beyond the annotations, it discloses concrete behavior: the tool is LOCKED on this server and 'returns a refusal and sends nothing to the SAP system', which is exactly the kind of outcome context annotations cannot express. This is consistent with readOnlyHint=true and destructiveHint=false, though the config instructions contradict themselves ('does not enable writes' followed by 'Set ABAP_ALLOW_WRITE=true').

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, but the ordering is poor: the most decision-relevant fact (it refuses and sends nothing) is buried at the end, while the middle sentence about ABAP_MODE and ABAP_ALLOW_WRITE is confusing and self-contradictory. Front-loading the lock state would make it much tighter.

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?

With zero params, no output schema, and annotations covering the safety profile, the description only needs to convey behavior, which it largely does. However, the contradictory environment-variable advice leaves an agent unsure whether the lock can be lifted, so it is not fully complete.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. The description adds no parameter detail, but none is needed.

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 opening sentence states a specific verb and resource ('Delete a BOPF business object'), which is enough to separate it from siblings like abap_bopf_edit and abap_bopf_test. The subsequent sentences muddy this by declaring the operation is locked, but the core purpose is still identifiable.

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?

It never names an alternative tool or states a when-to-use condition relative to siblings. The ABAP_ALLOW_WRITE/ABAP_MODE configuration guidance is not usage guidance for selecting this tool, and it is internally tangled, so the agent gets little help deciding when to call it.

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