abap_fpm_read

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description does add genuinely non-obvious behavior: a throwaway bridge class is deployed on every call, and on this server the call returns a refusal without touching SAP. Those additions are valuable, but the middle sentences about ABAP_ALLOW_WRITE/ABAP_MODE are self-contradictory and reduce trust in the rest.

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?

Purpose is front-loaded, which is good, but the body is rambling and internally contradictory ("ABAP_ALLOW_WRITE does not enable writes" followed by "Set ABAP_ALLOW_WRITE=true"). Sentences do not earn their place; the lock explanation could be one clear line.

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, no-output-schema tool the definition is nearly complete: it explains that the call returns a refusal and sends nothing to SAP, which is the key operational fact. But the garbled lock/env-variable narrative leaves an agent unsure whether the tool can be invoked at all, and no sibling alternative is named.

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?

There are zero parameters, so the schema is complete by default (baseline 4). However, the description introduces ABAP_ALLOW_WRITE and ABAP_ALLOW_PACKAGES in an imperative tone ("Set ...=true") that could be mistaken for invocation parameters rather than server environment configuration. That ambiguity costs a point.

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 clause gives a specific verb and resource: "Read SAP FPM/FBI screen configurations." That is enough to distinguish it from generic siblings like abap_read or abap_search. However, the remaining four sentences are consumed by lock-state and environment-variable talk that obscures rather than sharpens the purpose.

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?

The description does signal that the tool is LOCKED and that "Calling it returns a refusal and sends nothing to the SAP system," which is a when-not-to-use hint. But it immediately undercuts itself with "Set ABAP_ALLOW_WRITE=true," leaving the agent unable to tell whether the tool is usable. No alternatives or routing guidance to siblings is given.

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