sap_select_alv_context_menu_item

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is already covered. The description adds genuine behavioral context beyond that: the menu must be in an opened state, and the toolbar_button_id parameter collapses open+select into one atomic operation rather than two dependent calls. It stops short of saying what the selected command actually triggers or what happens on failure, so it falls short of a 5.

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-loads purpose, then the workflow, then parameter semantics, using a compact bulleted list for the enum decoding. Every sentence adds information -- no restatement of the title, no filler.

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?

Output schema exists, so return values need no prose; annotations cover the safety profile; the description covers the state prerequisite, the alternative call sequence, and all meaningful parameter formats. Nothing an agent needs in order to invoke this correctly 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 description coverage is 0%, so the description carries the full burden and does so well: it enumerates the accepted formats for menu_item_id (function code like @M00006, visible text, or position descriptor), decodes every select_by enum value including the auto heuristic, and explains toolbar_button_id's role in the atomic path. Only grid_id is left implicit, which is reasonable given the name.

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?

Opens with a precise verb+resource ('Select an item from an opened ALV context menu') and immediately scopes it away from the siblings it could be confused with, sap_press_alv_toolbar_button (opens menus) and sap_select_menu. An agent can distinguish it from those without reading either schema.

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?

Explicitly states the two usage paths -- call sap_press_alv_toolbar_button first, or pass toolbar_button_id for a single atomic call -- and marks the atomic path as recommended. It even points to where the available items are listed, leaving nothing to inference.

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