sap_press_button

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

Annotations already indicate it is not read-only nor destructive. The description adds value by noting it returns screen info to detect navigation or popups, clarifying the post-action effect.

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 concise sentences: action, return value benefit, and discovery tips. Every sentence adds value without redundancy.

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 simple one-parameter tool with an output schema (implied), the description covers purpose, parameter source, and return value. Could explicitly state it applies to both toolbar and on-screen buttons.

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?

With 0% schema coverage, the description compensates by explaining how to find button IDs, but does not specify the exact format or source of the button_id parameter beyond type 'string'.

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?

Clearly states 'Press a button on the current SAP screen' with a specific verb and resource, distinguishing it from sibling tools like sap_select_checkbox or 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?

Provides actionable guidance on discovering button IDs via sap_get_toolbar_buttons and sap_get_screen_elements, but does not explicitly contrast with other pressing tools (e.g., sap_press_alv_toolbar_button).

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