Read Classic ABAP Screen or GUI Status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety contract is covered. The description adds one behavioral fact beyond those: the tool operates 'through an opt-in same-origin classic bridge,' implying an enabling prerequisite — but it doesn't say the bridge must how it affects calls or error behavior when not enabled. This matches the pattern where annotations carry the safety profile and the description adds partial constraint context without contradiction.

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 description is a single, efficiently worded sentence with the verb and resource front-loaded before the mechanism qualifier. Every phrase contributes — though being 'opt-in same-origin classic bridge' is dense, jargon-laden, and could be clearer for an agent, it is not filler. The title reinforces the artifact without duplicating the full sentence, staying tight.

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 the low complexity (zero parameters), rich annotations, and presence of an output schema, the description does not need to explain return formats. But it leaves important gaps: how the tool selects which screen/GUI status to read with no parameters, what 'opt-in same-origin' requires of the caller, and how failures manifest when the bridge is unavailable. An agent could call it correctly but would be blind to the mechanism prerequisite.

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 has 0 parameters, so the schema provides no semantics to clarify; per the rubric, a 0-parameter tool gets a baseline of 4. The description names the target artifact types (Screen/Dynpro or GUI Status) which is the only relevant meaning an agent needs. Nothing is missing here from a parameter-class documentation it implies how the target is selected, no parameter-level deficit.

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 title and description name a specific verb ('Read') and resource ('Screen/Dynpro or full GUI Status document'), which clearly identifies a distinct artifact type on the SAP side. This artifact is not targeted by any sibling, including sap.source.read, sap.ddic.read, and sap.text_elements.read. However, the phrase 'opt-in same-origin classic bridge' is jargon that obscures what exactly is read and what the bridge is, keeping this short of a 5.

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 gives no guidance on when to use this tool versus alternatives such as sap.classic.write, sap.source.read, sap.ddic.read, or sap.text_elements.read. It also never states the implied prerequisite — the opt-in bridge must be enabled — nor what context is required (the 0-parameter schema offers no selection). An agent cannot determine from this text when it is the right tool.

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