cluster_configure

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

The description includes parameter semantics that extend beyond annotations (e.g., specific behavior for 'ha', 'drs', 'drs_behavior'), and does not contradict annotations. However, it omits side effects or prerequisites.

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?

The description is concise, uses a clear docstring format, and front-loads the key purpose. It could be slightly tighter but is well-structured.

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?

Given the tool's moderate complexity (5 params, 1 required) and existence of an output schema, the description adequately covers the core functionality and parameters without extraneous detail.

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?

With 0% schema description coverage, the description compensates by explaining each parameter's purpose and allowed values (e.g., 'True/False/None' for ha/drs), which the input schema lacks.

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 starts with '[WRITE] Reconfigure cluster HA/DRS settings.' This clearly specifies the action (reconfigure) and resource (cluster), and distinguishes it from sibling tools like cluster_create and cluster_delete.

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 description implies usage for modifying an existing cluster's HA/DRS settings via parameter details, but does not explicitly state when to use versus alternatives or provide when-not conditions.

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