reload_connections

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

The description reveals a meaningful side effect beyond annotations: it 'closes existing connection pools and loads new configuration', which warns the agent that active pooled connections will be torn down. It does not contradict the idempotent/non-destructive hints and adds useful operational context, though failure-mode behavior is left undisclosed.

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?

Two sentences contain no filler: the first states the action and its benefit, the second states the side effect. All information is front-loaded and 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 zero-parameter administrative reload, the description is nearly complete: it identifies the trigger, the source file, and the main side effect. There is no output schema and no mention of validation/error behavior if the file is invalid, which an agent might need to anticipate, but the core call is clear.

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 tool has no parameters and the schema reflects that fully, so the baseline of 4 applies. The description doesn't need to document any parameters; the only relevant details are the source file and reload behavior, both covered.

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 names a specific verb ('reload') and resource ('connections.json') and clearly distinguishes this administrative action from read-only sibling tools like list_connections or query. It also states the operational benefit ('without restarting the MCP server'), so the agent knows exactly what action this tool performs.

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 phrase 'without restarting the MCP server' implies the intended use case: applying connection configuration changes at runtime. It does not explicitly name an alternative or state when not to use it, but siblings are mostly query/read tools, and the distinction is reasonably inferable.

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