create_incident

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

No annotations provided; the description only states it creates an incident record. No disclosure of side effects, required permissions, error behavior, or process details.

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?

Two sentences, front-loaded with purpose, no wasted words. Efficiently communicates core action and parameter format.

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 one parameter with a nested object and no output schema, the description is insufficient. No information on what the tool returns, side effects, or how to use it among many sibling tools.

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 0%. The description adds that fields is a dict of ServiceNow field name->value, which provides minimal context beyond the schema's 'object' type. Lacks specifics on valid field names or required fields.

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 it creates a new incident record, using a specific verb and resource. It distinguishes from siblings like get_incident, update_incident, and list_incidents, which have different actions.

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 on when to use create_incident versus alternatives like create_request or create_table_record. Lacks prerequisites, context, or conditionals.

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