cluster_rebind

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

No annotations provided and the description does not disclose any behavioral traits such as side effects, permissions required, or what happens under each action. This is a significant gap for a tool with multiple modes.

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 very short (one sentence) and lists actions, but lacks structure or headers. It is concise but at the expense of clarity.

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 complexity (6 parameters, multiple sub-actions, an output schema exists), the description is grossly incomplete. It does not explain the return value, how to choose actions, or how parameters interact.

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 must compensate but provides no information about any of the 6 parameters (action, cluster_slug, report_path, dry_run, auto_create_new, folder). The agent has no guidance on how to set these.

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 it is a consolidated tool for cluster rebind and lists four sub-actions (propose, apply, list_orphans, status), but does not explain what 'rebind' means or how this tool differs from sibling tools like 'propose_cluster_rebind' and 'apply_cluster_rebind'.

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?

No guidance on when to use this consolidated tool versus the separate sibling tools for each action. No prerequisites or context for use are provided.

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