Deletes a custom field definition and removes that field from all entities in the Conduyt account.
Delete a custom field definition. Removes the field from all entities.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Custom field UUID |
Changes observed during successful MCP inspections.
v4.71.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden; it does disclose the important cascading effect that the field is removed from all entities, which signals broad destructive impact. It omits whether the operation is reversible, what happens to existing values, permission requirements, or error behavior when the field is in use.
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 short sentences, action first and consequence second. No filler or restatement.
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?
Adequate for a one-parameter delete with no output schema: the agent knows what it does and that it affects all entities. Missing irreversibility/confirmation and permission context reduce it below complete for a destructive operation with no annotation safety hints.
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?
Single required `id` parameter with 100% schema description coverage ("Custom field UUID"), so the schema already supplies the needed semantics. The description adds nothing about the identifier or its format, which is acceptable at this coverage level.
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?
States a specific verb and resource ("Delete a custom field definition") and clarifies the object of deletion is the definition rather than the stored values. Siblings list_custom_fields/create_custom_field/update_custom_field are implicitly distinguished by the verb, though none is named explicitly.
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 versus update_custom_field, no prerequisites, and no warning that deletion is permanent. An agent must infer that this is the terminal, irreversible option in the custom-field lifecycle.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.