opn_reconfigure_haproxy

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

Discloses that changes take effect immediately, no savepoint protection, and that reconfigure starts the service. No annotations provided, so description carries full burden. Could mention potential service interruption but is sufficiently transparent for this type of tool.

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?

Description is concise but includes necessary warnings and notes. Front-loaded with purpose, then usage context and important reminders. Slightly verbose due to multiple warnings but each is essential.

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: purpose, usage context, prerequisite (plugin), required sequence (configtest), behavior (immediate, no savepoint), and output format. Zero-parameter tool with high completeness given no annotations.

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?

No parameters defined in schema. Baseline score of 4 applies. Description does not need to add parameter information, and it doesn't repeat anything from 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?

Clearly states verb 'apply' and resource 'pending HAProxy load balancer configuration changes'. Distinguishes from siblings by indicating it is for applying changes after making HAProxy configuration modifications, and explicitly warns against calling haproxy/service/start.

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?

Provides explicit when-to-use: after making HAProxy configuration changes. Includes important warnings: always call configtest before, do not call start after. Also notes lack of savepoint protection and requirement for os-haproxy plugin.

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