qt_detach

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

Without annotations, the description carries the full burden of behavioral disclosure. It clearly states that purge=True 'ejects the injected DLL' and 'deletes the session's saved files' and marks the action as 'irreversible.' It also discloses the consequence of purge=False: the DLL stays loaded until the process exits.

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 three sentences, with the core purpose in the first line. Each subsequent sentence explains the purge behavior and links it to a real-world consequence, with no fluff.

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?

The description covers the purpose, parameter behavior, irreversible side effects, and a practical use case. It doesn't detail return values or error handling, but an output schema exists, and the tool is simple enough that this is not a major gap.

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 provides only names and types, but the description adds deep semantic meaning for purge: default False, what it does, and why it matters. The session_id parameter is not explicitly described but is implied by the term 'session'; the description's detail on purge compensates for the 0% schema coverage.

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 opens with a clear, specific action: 'Disconnect from a Qt process session,' which uses a precise verb and resource. It distinguishes itself from sibling tools like qt_attach and qt_build through its focus on session teardown.

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 explicit guidance on when to use purge=True: 'Use purge=True before rebuilding the library: otherwise the DLL file stays locked by the target process and qt_build fails.' It also explains the alternative behavior with purge=False, helping agents choose the right parameter value.

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