Batch Update Records

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

With no annotations, the description should disclose critical behavior. It only states 'modifies records on the ServiceNow instance,' omitting details like permission requirements, rollback behavior, error handling (though partially covered by stop_on_error param), and the impact of partial failures. This is insufficient for a batch mutation tool.

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 concise, with two sentences and an important note. It front-loads the main purpose. However, it could be slightly more structured (e.g., bullet points for key points) without losing conciseness.

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 complexity of batch updates (3 parameters, nested objects, no output schema, no annotations), the description is too minimal. It lacks context on authentication (instance parameter), success/error output, and partial failure semantics. Better completeness is expected for a tool with many siblings.

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%, with each parameter clearly documented in the schema. The description reiterates that each update specifies table, sys_id, and field data, but adds no extra meaning beyond the schema. Baseline score of 3 is appropriate.

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 the verb ('Update'), resource ('multiple records across one or more ServiceNow tables'), and context ('in a single batch'). It effectively distinguishes from sibling tools like 'batch_create_records' and 'query_update_records' by emphasizing the batch update nature.

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 provides no guidance on when to use this tool versus alternatives such as 'batch_create_records' or individual updates. It does not mention prerequisites, exclusions, or recommended scenarios, leaving the agent without decision support.

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