cluster_configure

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

Annotations indicate it's not read-only, not destructive, not idempotent, and open-world. The description confirms mutation via '[WRITE]' and specifies which settings change. No contradictions. It adds context like possible values for drs_behavior.

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 front-loaded with the purpose and uses a clear Args section. It could be slightly more concise, but every sentence adds value. No wasted words.

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 has 5 parameters (1 required) and an output schema, the description covers the essential parameter details. It does not explain return values, but the output schema handles that. Adequate for a reconfiguration tool.

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?

Schema description coverage is 0%, but the description compensates by listing each parameter with allowed values (e.g., ha: True/False/None, drs_behavior: 'fullyAutomated'/'partiallyAutomated'/'manual'). This adds meaningful semantics beyond the schema's type-only definitions.

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]' indicating the operation type, then clearly states 'Reconfigure cluster HA/DRS settings.' It lists the specific settings modified (HA and DRS), distinguishing it from sibling tools like cluster_create, cluster_delete, and cluster_info.

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 use for modifying existing cluster HA/DRS settings but does not explicitly state when to use this tool versus alternatives like cluster_create or cluster_info. No when-not-to-use guidance is provided.

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