Permanently removes a Convocore agent variable using its variableId, so stale or unwanted variables no longer affect agent behavior.
Permanently delete a Convocore agent variable by variableId.
| Name | Required | Description | Default |
|---|---|---|---|
| variableId | Yes |
Changes observed during successful MCP inspections.
v2.6.17Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The word 'Permanently' reinforces irreversibility, but the description says nothing about cascade effects on agent prompts that reference the variable, behavior when the variableId does not exist, or what is returned.
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 front-loaded sentence with the destructive qualifier first and the resource second. Nothing is wasted or buried.
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 one-parameter delete with rich annotations covering destructiveness and idempotency and no output schema, the description supplies the essential scope. Only error/not-found behavior and the source of variableId remain unstated, which are minor for this tool shape.
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 0%, so the description must carry the param burden, but 'by variableId' only restates the parameter name and type already in the schema. It gives no format, no hint on where the ID comes from (e.g., list_agent_variables), and no note that it is required.
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 ('permanently delete'), a specific resource ('Convocore agent variable'), and the lookup key ('by variableId'). It is clearly distinguishable from delete_agent, delete_kb_doc, and delete_agent_tool by resource, though it does not explicitly name those 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 versus update_agent_variable (to clear a value) or the sibling delete tools, and no prerequisites such as required permissions or confirmation steps. The agent must infer all usage conditions 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.