cluster_add_host

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

The description includes the '[WRITE]' tag which aligns with the annotations (readOnlyHint false). However, it does not disclose additional behavioral traits such as side effects, reversibility, or required privileges. The annotations already provide some context, but the description adds minimal extra value.

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 extremely concise, consisting of a one-line summary and a parameter list. No redundant or extra text, making it easy to parse quickly.

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?

The description covers the basic purpose and parameters, but lacks usage context, prerequisites, or behavior details. Given the presence of an output schema and similar sibling tools, more completeness would be beneficial.

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 description includes a docstring explaining each parameter: cluster_name, host_name, and optional target. This adds semantic meaning beyond the schema, which only provides titles and types. Schema description coverage is 0%, so this compensation is valuable.

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] Move a host into a cluster.' which clearly states the action and resource, distinguishing it from siblings like 'cluster_remove_host'. However, the term 'move' is slightly ambiguous as the operation actually adds a host to a cluster.

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 provides no guidance on when to use this tool versus alternatives, such as 'cluster_configure' or 'cluster_remove_host'. It does not mention prerequisites or conditions for use.

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