dolphin_disconnect

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It does not explain what 'disconnect DAP' entails, potential side effects, or whether 'terminateDolphin' kills a process forcefully. The lack of detail is significant for an operation that may terminate a process.

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 that efficiently conveys the core functionality and the optional behavior. No unnecessary words are present.

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 tool that may terminate a process, and with no annotations or output schema, the description is incomplete. It omits critical details such as side effects, whether the process is terminated gracefully, and any required permissions or states.

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 0%, meaning the single parameter 'terminateDolphin' is not documented in the schema. The description does clarify that it 'optionally terminate[s] a Dolphin process started by this server', which adds meaning. However, it does not specify the default (false) or the implications of setting it to true.

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: disconnect DAP and optionally terminate a Dolphin process. It distinguishes itself from sibling tools like dolphin_start and dolphin_connect by focusing on disconnection. However, no explicit sibling differentiation is provided in the text.

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 gives no guidance on when to use this tool versus alternatives, nor any preconditions or warnings. It merely states what the tool does, leaving the agent to infer usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.