Export Record as XML

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

Annotations already declare readOnlyHint=true, so the tool is known to be a safe read operation. The description adds valuable behavior context by naming the unload XML format and the endpoint, and noting the XML can be imported into another instance. No contradiction with annotations.

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 succinct and front-loaded with the core purpose, followed by a bulleted list of use cases. Every sentence earns its place with no filler.

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 read-only export tool with three fully documented parameters and no output schema, the description covers the key context: purpose, format, endpoint, and likely use cases. The XML output is implied by the phrase 'generate ServiceNow-native XML,' which is sufficient for this complexity level.

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%, with all three parameters (table, sys_id, instance) fully described. The description does not add additional parameter-level detail beyond the schema, but it reinforces the single-record scope and the XML format, matching the baseline for well-documented schemas.

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 the tool's verb and resource: 'Export a single record from a ServiceNow instance in unload XML format.' It specifies the endpoint and distinguishes itself from the sibling import_records_xml by emphasizing the export direction and single-record scope.

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 provides four concrete common use cases (backup, transfer, comparing, update sets) that establish clear context for when to use the tool. It does not explicitly mention alternatives or when-not-to-use, so it stops short of a 5.

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