Delete ServiceNow Record

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

Annotations already declare destructiveHint=true, but the description adds 'irreversible' and 'permanently removes the record,' going beyond the annotation to explain the consequence. No contradiction exists, and the caution label provides additional safety context.

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 compact and well-organized: action, args, returns, and warning. Each sentence serves a purpose, and the prominent destructive warning is valuable. No fluff.

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 simple 2-parameter delete, it covers the core aspects: action, parameters, return value, and destructive warning. The absence of an output schema is offset by the 'Returns: Confirmation of deletion' note. It doesn't address edge cases like not-found, but that's not essential for this tool.

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%, so the schema already documents both table and sys_id. The description repeats the parameters without adding extra format details or usage nuances beyond what the schema provides.

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 'Permanently delete a ServiceNow record by sys_id' – a specific verb and resource. It clearly distinguishes itself from siblings like create, update, and bulk_delete by focusing on a single record deletion.

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?

It provides a clear when-not instruction: 'Use only when deletion is explicitly requested.' It implies single-record scope via sys_id but does not explicitly mention alternatives like bulk_delete for multiple records, so it misses the top tier.

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