servicenow_create_flow

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

No annotations are provided, so the description carries the full behavioral burden. It does not state what permissions or role are needed, whether created flows are immediately active/published, whether name collisions are rejected, or what the response contains. Naming the table is the only real behavioral hint.

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 single front-loaded sentence with no wasted words; the verb and resource lead. It is terse to the point of under-specification, but nothing in it is redundant or padded.

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?

For a mutation tool with no annotations, no output schema, and a free-form nested object parameter, the description is far from sufficient. An agent cannot know what fields to supply or what success looks like.

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?

The single parameter is a free-form object with additionalProperties allowed and 0% schema description coverage, so the agent has no documented key names or required fields. The description names the table sys_hub_flow, which is a weak signal about which fields are valid, but it does not compensate for the total absence of parameter documentation.

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 resource (ServiceNow Flow record) and even names the target table sys_hub_flow, which distinguishes it from the generic servicenow_create_record sibling. It stops short of spelling out how it differs in intent from create_record, but the resource is 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?

There is no guidance on when to use this over servicenow_create_record or the other create-style siblings, no prerequisites, and no exclusions. The agent must infer that 'flow' means a sys_hub_flow row rather than any generic record.

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