sap_set_batch_fields

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

Annotations indicate a non-readonly, non-destructive operation. The description adds specific behaviors: validate triggers status-bar feedback, validate is skipped if no fields set, and skip_readonly silently handles readonly fields. No contradictions.

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?

Extremely concise: two-line purpose, one-line efficiency note, then parameter docs. No redundancy. Information is front-loaded and easy to scan.

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 all parameters and key behaviors. Output schema exists, so no need for return value description. Could mention prerequisites (e.g., connection to SAP system) but implied by sibling tools. Very strong overall.

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%, so the description fully compensates by explaining each parameter: fields (dict mapping), validate (boolean with feedback), skip_readonly (boolean for skipping readonly fields). Details beyond schema.

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 it sets multiple field values at once and explicitly distinguishes it from the sibling tool sap_set_field by highlighting efficiency for bulk operations.

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 clear guidance: use when setting multiple fields (more efficient than repeated calls). The parameters validate and skip_readonly also have usage descriptions, but no explicit when-not-to-use scenarios.

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