abap_bopf_edit

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

Annotations already declare readOnlyHint/idempotentHint, so the bar is lower, but the description adds real context beyond structured fields: the server is LOCKED, the call 'returns a refusal and sends nothing to the SAP system,' and the enabling variables are named. The middle sentence is muddled ('ABAP_ALLOW_WRITE does not enable writes' immediately followed by 'Set ABAP_ALLOW_WRITE=true'), which blunts an otherwise strong disclosure.

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?

The critical fact (LOCKED / refusal) appears in sentence two rather than being front-loaded, and the enablement sentence is self-contradictory about what ABAP_ALLOW_WRITE actually does. Four sentences deliver essentially two ideas, and the config guidance could be compressed into one clause.

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 zero-parameter tool with no output schema, the description covers the essentials an agent needs: what it nominally does, that this server refuses the call, that nothing reaches SAP, and how writes would be enabled. Only the confused config sentence keeps it from being fully self-sufficient.

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 the schema carries no semantic burden and the baseline for empty parameter sets is 4. The variables mentioned (ABAP_ALLOW_WRITE, ABAP_ALLOW_PACKAGES) are server configuration, not inputs, so there is no parameter meaning left to add.

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 first sentence names a concrete verb and resource: 'Make one design-time edit to a BOPF business object, or create one,' which is far more specific than a restatement of the name. However, it never distinguishes itself from the adjacent siblings abap_bopf (read), abap_bopf_delete, or abap_bopf_test, so an agent must infer the split from names alone.

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?

Usage is implied by the resource type ('design-time edit to a BOPF business object'), and the description states the precondition for actually writing (ABAP_ALLOW_WRITE=true, optional ABAP_ALLOW_PACKAGES). It gives no when-not guidance and never says why an agent would pick this over abap_enh, abap_write, or abap_bopf_delete.

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