Export an escalation chain definition by providing its ID to retrieve the configuration details needed for analysis or backup.
Export an escalation chain definition
| Name | Required | Description | Default |
|---|---|---|---|
| escalation_chain_id | Yes | Escalation chain ID |
Changes observed during successful MCP inspections.
v4.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the 'export' behavior but doesn't elaborate on what the output format is, whether a file is generated, or any side effects. This is minimal added value beyond the 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?
A single sentence that is direct and front-loaded. No filler words, and the purpose is immediately clear. Excellent conciseness for a simple tool.
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 the tool has one simple parameter and annotations cover safety, the description is minimally sufficient. However, it omits what 'export' actually returns (file, JSON, etc.) and doesn't clarify when export is more appropriate than get_escalation_chain. For an export tool, some note about the output behavior would improve completeness.
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 100% with the parameter described as 'Escalation chain ID', so the schema already documents the parameter. The description adds no additional meaning about the parameter beyond what is in the schema. Baseline 3 is appropriate.
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 uses a specific verb 'export' and resource 'escalation chain definition', clearly indicating the action. It distinguishes from the sibling 'get_escalation_chain' by implying a file/download-oriented operation, though it doesn't explicitly differentiate the export format from a simple retrieval. The pattern matches other export_* siblings.
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 this tool versus alternatives like get_escalation_chain or export_logsource. The description doesn't state any prerequisites, context, or exclusions. An agent must infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.