Remove contract templates from the eSignatures system to manage your template library and maintain organized workflows.
Deletes a contract template.
| Name | Required | Description | Default |
|---|---|---|---|
| template_id | Yes | GUID of the template to be deleted. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Deletes' communicates a destructive action, but it does not mention irreversibility, cascading effects, permissions, or what happens after deletion. Additional behavioral context is missing.
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 a single, front-loaded sentence with no wasted words. It states the action and resource directly and is appropriately concise for a simple one-parameter 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?
For a simple one-parameter deletion tool, the description plus schema provides enough to invoke it. However, it lacks behavioral details such as deletion permanence, potential restrictions, and side effects, so it is adequate but not fully complete.
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 input schema already fully documents template_id as a required GUID, with 100% schema description coverage. The description adds no extra semantic detail, but none is needed beyond what the schema provides, so a baseline score of 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 'Deletes a contract template.' clearly identifies the action (delete) and the resource (contract template). This distinguishes it from siblings like delete_contract, which targets contracts rather than templates.
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 implies when to use the tool: when the goal is to remove a contract template. However, it gives no explicit context about prerequisites, exclusions, or how it compares to alternatives like delete_contract or withdraw_contract.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.