Create ServiceNow record

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

There are no annotations, so the description carries the disclosure burden. It says a record is created but does not mention that the default plan mode can return a non-mutating preview unless 'apply' is true, nor does it disclose side effects or write-mode requirements.

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 short, front-loaded single sentence with no filler. Every word earns its place, and the core operation is stated immediately.

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?

No output schema exists, and the description does not explain return behavior, the apply/preview default, or error conditions. For a mutation tool with a notable 'apply' nuance, this is too sparse to fully enable a correct call.

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 100%, so the input schema fully documents 'table', 'fields', and 'apply'. The description adds little beyond the phrase 'given field values', which loosely maps to the 'fields' parameter without providing extra semantic value.

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 states a specific verb ('Create') and a clear resource ('a new record in a table with the given field values'). It is unambiguous and distinguishes itself from siblings like servicenow_update_record, servicenow_query_table, and servicenow_delete_record.

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?

No guidance is given on when to choose this tool over alternatives, prerequisites, or conditions such as write mode or an existing table. The only usage signal is the verb itself, which implies the purpose but does not explicitly route the agent.

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