system_reconnect

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

Describes the validation-before-swap behavior and return value. Annotations provide no safety info, so description compensates well. Minor omission: does not mention potential temporary unavailability.

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, well-structured, and front-loaded. Every sentence adds value without redundancy.

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?

Fully explains purpose, usage, behavior, and return value. No output schema, but return shape is described. Complete given tool simplicity.

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?

Input schema has no parameters, but description mentions a 'host' parameter. This is misleading and contradicts the schema. For 0-parameter tools, baseline is 4, but the error reduces score.

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 tool rebuilds a pooled Docker client to recover a wedged connection, using specific verbs and resources. It distinguishes itself from sibling tools by focusing on connection recovery.

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 describes when to use (recover wedged connection) and when not (cannot retarget daemon). Provides alternative action (edit config and restart).

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