Remove a lead scoring rule from Conduyt by its UUID to keep scoring criteria current and prevent outdated rules from affecting lead scores.
Delete a lead scoring rule.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Scoring rule UUID |
Changes observed during successful MCP inspections.
v4.71.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It implies a destructive mutation but says nothing about irreversibility, permission requirements, or whether associated scores or rule assignments are affected.
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 short sentence with no wasted words, and the destructive action is front-loaded. It is efficient, though the terseness leaves no room for helpful behavioral context.
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 destructive delete tool with no annotations and no output schema, the description should disclose more about side effects, reversibility, or return behavior. The one-line description is not complete enough for an agent to call it safely and confidently.
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%, and the sole parameter id is documented as "Scoring rule UUID" in the schema. The description adds no additional semantic detail about the identifier, so the baseline 3 applies when the schema does the work.
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 gives a specific verb and resource ("Delete a lead scoring rule"), so the operation is unambiguous. However, it does nothing to distinguish this from the many other delete_* siblings, such as conduyt_delete_custom_field or conduyt_delete_pipeline.
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?
There is no guidance on when to use this versus conduyt_update_scoring_rule, conduyt_list_scoring_rules, or conduyt_recalculate_scores. The sentence states the operation but provides no prerequisites, exclusions, or alternative-routing advice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.