system_reconnect

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

Describes the safety mechanism (validates before swapping) and default host behavior. Annotations are neutral, so description adds valuable context.

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?

Concise and well-structured: action, safety detail, constraints, alternatives, and return type in a compact paragraph.

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?

Covers all relevant aspects: usage, behavior, constraints, and return value. No output schema needed as return is described.

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 description mentions a 'host' parameter ('when host is omitted'), but the input schema has no properties. This creates confusion and contradicts the schema.

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: rebuild a pooled Docker client to recover a wedged connection. It distinguishes itself from siblings like system_close and host_list.

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?

Explicitly says when to use (to recover a wedged connection), when not (cannot retarget daemon, must restart to change), and provides alternatives (system_close, host_list).

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