sap_click

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

With no annotations, the description carries the full behavioral burden, yet it only discloses the coordinate origin. It says nothing about focus/window requirements, mouse-down/up timing, whether the click has irreversible side effects in the SAP UI, or what the return_screenshot options do.

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?

A single front-loaded sentence with no filler — the scoping detail comes first. It is arguably under-specified rather than overly long, but on pure conciseness it is efficient.

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 4-parameter, zero-annotation, no-output-schema tool, one sentence is insufficient: the screenshot-return mechanism and folder target are unexplained, and no side-effect or failure behavior is described.

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 phrase 'physical screenshot pixels relative to the selected SAP window' effectively defines x and y, which is real added value over a 0%-coverage schema. However, return_screenshot (5 enum options) and as_file_target_folder are entirely undocumented, including the evident dependency of the folder parameter on return_screenshot='as_file'.

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?

A specific verb (click) on a specific resource (screenshot pixels) with the coordinate frame named ('relative to the selected SAP window'), which meaningfully distinguishes it from sap_move_mouse and coordinate-free input tools like sap_type/sap_press. It does not, however, name or contrast with any sibling tool.

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?

No when-to-use guidance, no prerequisites, and no routing to alternatives such as sap_press, sap_set_field, or sap_send_vkey for element-level interaction. The agent must infer that this is the fallback for pixel-precise clicking.

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