sap_set_batch_fields

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

Annotations already provide readOnlyHint=false and destructiveHint=false, so the description's mention of 'fill in' and 'more efficient' adds limited behavioral context. It does not contradict annotations but lacks disclosure of potential side effects (e.g., screen navigation, validation behavior). With annotations carrying the safety profile, a score of 3 is appropriate.

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?

The description is two sentences long with no wasted words. The first sentence clearly states the action, and the second provides usage context and efficiency comparison. It is front-loaded and earns every word.

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?

Given the tool has an output schema (not shown) and the description covers purpose and usage well, it is fairly complete. However, it could briefly mention the behavioral effect of the 'validate' or 'skip_readonly' parameters, though these are described in the schema. Overall, adequate for a batch input 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 100%, so the input schema already documents all three parameters. The description reiterates the 'dict of field_id to value' pattern for the 'fields' parameter but adds no additional semantic detail beyond the schema. Baseline for high coverage is 3.

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 uses a specific verb-resource combination ('Fill in multiple input fields at once') and explicitly distinguishes from the sibling tool sap_set_field by stating it is 'more efficient than repeated sap_set_field calls'. This makes the purpose clear and differentiated.

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?

The description says to use this 'to fill a form or selection screen in one call' and compares it to repeated calls of sap_set_field, providing clear guidance on when to use. However, it does not explicitly mention scenarios where it should not be used (e.g., when field-by-field validation is needed), preventing a perfect score.

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