sap_press_button

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false) by disclosing post-condition output ('Returns screen info after the press so you can detect navigation or popups') and a user-confirmation policy: presses that may save or ambiguous popup answers prompt the user and surface confirmed_by_user: true. That is exactly the kind of consequence/auth context an agent needs for a mutating click.

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?

Front-loaded with the core action, then progressively adds discovery, long-text, and confirmation details — all sentences are actionable rather than filler. Slightly dense for a single-parameter tool, but nothing is clearly redundant.

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?

An output schema exists, so return values need not be spelled out, yet the description still notes that screen info is returned and how to interpret it for navigation/popup detection. Combined with the ID-discovery and confirmation guidance, an agent has enough to invoke this correctly; only the ALV-button disambiguation is missing.

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 for button_id is 0%, so the description must carry the load, and it does reasonably: it tells the agent where to obtain valid IDs (toolbar/screen-element discovery tools) and shows an example path syntax ('wnd[0]/sbar'). It stops short of stating the ID format rules in general, so a small gap remains.

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?

States a specific verb and resource ('Press (click) a pushbutton or toolbar button on the current SAP screen'), so an agent immediately knows the action and target. It differentiates from discovery siblings by pointing at sap_get_toolbar_buttons and sap_get_screen_elements, though it never explicitly contrasts itself with the very similar sap_press_alv_toolbar_button.

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?

Gives concrete usage context: discover IDs via sap_get_toolbar_buttons or sap_get_screen_elements, and a specific conditional workflow for message_has_long_text (press 'wnd[0]/sbar', then read with sap_read_list(window_id='wnd[1]')). It lacks an explicit when-not-to-use or a direct steer away from the ALV toolbar sibling, which leaves one plausible ambiguity unresolved.

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