Sap Double Click Cell

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so safety is partly covered. The description adds useful behavior context by noting the click typically opens detail views or drills down, and that it works on both ALV and TableControl. It does not say whether the double-click can mutate data, spawn a popup requiring sap_handle_popup, or change the screen context.

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?

Four short sentences, front-loaded with the action and effect, then the parameter semantics, then platform scope. Little waste; the only near-redundancy is restating 'column is the column name', which is quickly redeemed by naming the source tools.

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 described. However, for a drill-down action tool the description omits the obvious follow-up consequences (popups, new screens) and never explains table_id, which is required and undocumented in both schema and description.

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 description coverage is 0%, so the description must carry parameter meaning, and it does explain the two non-obvious ones: 'row is zero-based' and 'column is the column name' sourced from sap_read_table or sap_get_column_info. The third parameter, table_id, is never explained (how to obtain it, format), leaving a real hole given the zero coverage.

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 concrete verb+resource pair ('double-click a cell in a table/grid') and adds the likely effect ('opens details or drills down'). This is clearly distinguishable from the tree-oriented siblings (sap_double_click_tree_node, sap_double_click_tree_item) and from sap_select_table_row, though it never names an alternative explicitly.

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 parenthetical ('often opens details or drills down') implies why you would reach for this tool, and it points to sap_read_table / sap_get_column_info as the source of valid column names. There is no explicit when-to-use versus sap_select_table_row or sap_press_button, and no guidance on what to do after the drill-down occurs.

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