pws_remove_stable_worker

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

The annotations only flag destructiveHint=true, but the description adds crucial nuance: the default is preview (non-destructive) and the operation 'verifies removal.' This goes beyond the annotation by clarifying the dual-mode nature and safe default, making it a notable behavioral disclosure.

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: three short sentences with no wasted words. It front-loads the core purpose and immediately highlights the default behavior, which is exactly what an agent needs for a quick assessment.

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 primary purpose and preview default, but it omits details about the 'confirmed' parameter, the return value, and the behavior when minimum stable membership cannot be preserved. Given the tool's destructive potential and complexity, this is a noticeable gap.

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 bears the full burden of explaining parameters. It hints at the 'preview' parameter via 'Defaults to preview' but completely ignores 'stableId', 'contractId', and 'confirmed'—leaving the agent without a clear understanding of how to execute the actual removal.

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 clearly states the tool can preview or remove a worker from a stable while preserving a minimum stable membership. It uses a specific verb ('remove') and resource ('stable worker'), and the mention of 'preview' distinguishes it from other mutation tools like pws_add_stable_worker.

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 clear context: it is for removing a stable worker while maintaining minimum membership, and it defaults to preview, implying a safe exploratory use. However, it does not explicitly contrast with alternatives such as pws_release_worker or state when not to use this tool.

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