Sap Select All Table Control Columns

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation-safety profile is covered. The description adds the meaningful behavioral constraint that ALV grids are unsupported, but says nothing about what happens to existing selections when toggling, or whether the call requires a specific screen state.

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?

Two short sentences, zero filler, with the action stated first and the critical exclusion second. Nothing to trim.

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, and the tool is only two parameters deep. Still, for a state-changing table tool the description omits how `table_id` is identified and what the resulting selection state looks like, leaving gaps an agent would hit on first invocation.

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 largely doesn't. "Select or deselect" loosely maps to the `select` boolean, but `table_id` is never explained — no hint on its format or how to obtain it from sap_get_screen_info or similar.

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 pair (select/deselect) and a precise resource (all columns in a GuiTableControl), and explicitly excludes ALV grids, which is the main confusion axis among the many table/ALV siblings. An agent can tell this apart from sap_get_alv_toolbar and the row-selection tools without opening the 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?

"Does NOT work on ALV grids" is an explicit when-not condition, which is valuable given the many ALV siblings in the list. However, no alternative is named for the ALV case (e.g., which tool to use instead), and no preconditions for the table control are given.

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