sap_select_alv_context_menu_item

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

Annotations indicate readOnlyHint=false (modification) and destructiveHint=false, which are consistent. Description adds context about prerequisite (menu must be open) and atomic alternative. Could mention if selection triggers actions, but sufficient.

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?

Concise with 7 sentences; front-loaded main purpose. Every sentence adds value, no 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?

Covers purpose, prerequisite, alternative usage, parameter details, limitations. Has output schema, so return values are handled. Complete for a context menu selection tool.

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 is 0% but description explains menu_item_id can be function code, text, or position descriptor, and clarifies select_by modes with examples. Fully compensates for missing schema descriptions.

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 description clearly states 'Select an item from an opened ALV context menu,' specifying the action and resource. It distinguishes from sibling tools like sap_press_alv_toolbar_button and sap_select_menu by focusing on context menus.

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 explicit guidance: use sap_press_alv_toolbar_button first or pass toolbar_button_id for atomic call. Explains select_by options and limitations (no way to enumerate menu items).

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