sap_select_combobox_entry

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation-but-safe profile is known. The description adds the behavioral note that F4 does nothing on a dropdown, but omits what happens on an invalid key/text, whether an existing selection is overwritten, and any error signaling.

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?

Purpose is front-loaded and the sentences are short, but sentence 2 ('Accepts either the technical key or the visible display text') restates sentence 1's 'by its key or display value text', which is redundant filler. The F4/parenthetical contrast sentence earns its place but sits awkwardly.

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?

With an output schema present, return details are not needed, and annotations cover the safety profile. The description supplies the prerequisite, the alternative, and the accepted value formats, leaving only edge-case/error behavior unaddressed for a two-parameter mutation 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 description coverage is 0%, so the description must carry parameter meaning, and it does explain that key_or_value accepts either a technical key or visible display text and points to sap_get_combobox_entries for valid values. combobox_id remains undocumented, but the non-obvious parameter is well covered.

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 specific verb and resource ('Select an entry in a combobox/dropdown') plus the accepted value forms, so the agent knows exactly what the call does. It also differentiates itself from relatives by naming sap_get_combobox_entries as a prerequisite and sap_set_field as an equivalent alternative.

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?

'Use sap_get_combobox_entries first to see all valid options' gives a concrete prerequisite/order of operations, and the F4 remark steers the agent away from keyboard-driven selection. There is no explicit when-not or failure condition, but the routing context is clear.

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