sap_set_field

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the execution mechanism and window scoping, but says nothing about whether setting text fires SAP events/validations, what happens on an invalid element_id, permissions, or error/reversibility behavior for this mutation.

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?

A single front-loaded sentence with no filler, and the most important fact (setting text) leads. It is compact, though 'through SAP GUI ActiveX/COM scripting' is implementation detail that consumes space without helping selection.

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 no annotations, no output schema, and 0% parameter coverage, the description should compensate substantially. Instead it provides one sentence, leaving the agent without guidance on the element_id format, failure modes, or side effects — insufficient for a 2-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 neither element_id nor text is documented in structured data. The description's phrase 'literal text' loosely maps to the text parameter but gives no format, encoding, or length guidance, and element_id — the most opaque parameter — is not explained at all.

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 ('Set') and resource ('literal text') plus the mechanism (SAP GUI ActiveX/COM scripting) and scope (wnd[N] in this session). It clearly differentiates itself from sibling sap_type by emphasizing 'literal' value-setting, though it does not explicitly name that sibling.

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?

Usage is only implied: 'literal text' hints at direct value assignment versus the keystroke emulation of sap_type, and 'scoped to wnd[N]' hints at the targeting context. There is no explicit when-to-use, when-not-to-use, or named alternative among the many siblings.

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