probe_disconnect

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

With no annotations, the description carries the behavioral disclosure burden. It does reveal a key trait beyond the name: the disconnect frees the probe for flashing. But it does not disclose side effects, whether an active debug session is terminated, or whether reconnection is required afterward.

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?

One short sentence front-loads the action and immediately adds the key purpose in parentheses. There is no filler, no repetition of schema details, and every word earns its place.

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 single-parameter tool with no output schema, the description is adequately sized, but it leaves gaps: probe_id is undocumented, prerequisites and consequences of disconnecting are not stated, and alternative tool routing is not provided. It is minimally complete for a simple tool, but not fully complete.

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% and the description never mentions probe_id, so it adds no meaning beyond the parameter name and its default value. The single optional parameter is simple, but the description does not compensate for the missing schema documentation.

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 specific verb and resource, 'Disconnect the probe', and adds a concrete purpose: 'releases it for UV4 -f flash path'. It clearly distinguishes this tool from siblings like probe_connect, probe_halt, and probe_resume.

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 parenthetical gives useful context that the tool is used to free the probe for the UV4 -f flash path, implying a before-flash use case. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites such as the probe being connected or halted.

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