Reload Configuration

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

With no annotations, the description carries the full burden. It does disclose one behavioral trait ('Active connections are preserved') which is valuable, but it does not mention error handling, side effects, or what happens if the reload fails. It's a minimal disclosure.

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 short sentences with zero filler. The core action and key constraint are front-loaded, and every word contributes meaning. Excellent conciseness.

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, no-output-schema tool, the description adequately explains the action and a key behavior. It does not describe the return value or failure outcomes, but given the simplicity, it covers the essential context needed to invoke it correctly.

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 zero parameters, so the input schema is trivially complete. The description adds no parameter details because none are needed. Baseline for 0 params is 4, and there is no deficit.

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 states a specific verb ('re-read') and resource ('config') and adds a key modifier ('without restarting'). It is clearly distinct from sibling tools (web_search, fetch_page, etc.) which all involve data access rather than configuration management.

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' implies a scenario (apply config changes without downtime) but there is no explicit statement of when to use this tool versus alternatives, nor any exclusions or prerequisites. Usage context is only implicit.

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