Permanently removes a Convocore agent using its unique agentId, so you can clean up agents that are no longer needed.
Delete a Convocore agent permanently
| Name | Required | Description | Default |
|---|---|---|---|
| agentId | Yes | The unique identifier of the agent to delete |
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=false, and openWorldHint=true. The description adds useful irreversibility context with 'permanently,' but does not disclose cascading effects, required permissions, or whether associated data is removed.
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 language. For a simple one-parameter destructive tool, the size and structure are appropriate.
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's low complexity, complete parameter schema, and strong destructive annotations, the description is largely sufficient. The main remaining gap is that it does not explain what happens to related resources or whether confirmation is required.
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 schema fully documents the single agentId parameter at 100% description coverage. The description does not add any parameter-specific meaning beyond what the schema already provides, so the baseline score applies.
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 and resource: delete an agent, and adds the important qualifier 'permanently.' It distinguishes the target from siblings such as delete_agent_tool by naming a Convocore agent, though it does not explicitly route among related agent tools.
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 provides no explicit guidance on when to use this tool versus update_agent, clone_agent, or delete_agent_tool. Usage is only implied by the verb 'Delete,' with no preconditions, alternatives, or warnings about when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.