create_record

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Create', which clearly implies a write operation, but it does not mention permissions, idempotency, error conditions, or any side effects. This is a significant gap for a mutation tool without annotation support.

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 one concise sentence that front-loads the primary purpose. There is no redundant information or filler, making it optimally sized for quick comprehension.

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?

The tool is simple with two well-documented parameters and an output schema, so the description does not need to explain return values. However, the lack of behavioral transparency and usage guidance relative to sibling create_ci creates a gap. The description is minimally viable but not fully complete.

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% for both parameters (table_name and data). The description adds no additional meaning beyond the schema—it does not elaborate on how the data object should be structured or provide examples. The baseline of 3 applies since structured data carries the semantic load.

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 'Create a new record in any ServiceNow table', which specifies the action (create), resource (record), and scope (any ServiceNow table). The phrase 'any' distinguishes it from sibling tools like create_ci, which targets a specific table type, making the purpose unambiguous.

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 implies usage for generic record creation in any ServiceNow table, but it does not explicitly state when to use this tool versus specialized siblings like create_ci or update_record. There is no mention of alternatives or exclusions, leaving the decision to inference.

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