remove_connectionDelete a saved connection and its stored password to revoke access and remove sensitive credentials from Markdown Reader.
Delete a connection (and its stored password) from Markdown Reader.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The connection id (from list_connections) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It transparently discloses that the stored password is also deleted, which is a meaningful side effect. However, it does not mention irreversibility or any other potential consequences.
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, concise sentence that includes all essential information without any redundancy or extraneous detail.
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 deletion tool with one parameter and no return value schema, the description fully covers what the tool does and what input is needed. No additional context is necessary for an agent to invoke it correctly.
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 parameter description provides useful context by indicating that the id comes from list_connections, which helps the agent source the correct value. Since schema coverage is 100% and the description adds beyond a bare 'id', a score above baseline is warranted.
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 clearly states the action ('Delete') and the resource ('a connection'), and explicitly mentions that the stored password is also removed. This fully distinguishes the tool from siblings like add_connection or test_connection.
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 usage through the verb 'Delete' but does not provide explicit guidance on when to use this tool versus alternatives or any cautionary notes. No mention of when-not to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.