pws_add_stable_worker

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

The description adds meaningful behavioral context beyond annotations: 'PREVIEW OR ADD' and 'Defaults to preview' clarify that the tool may act destructively only when explicitly used to add, while 'Verifies membership' reveals a validation step. No contradiction exists with the destructiveHint annotation.

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 compact and front-loaded with 'BETA: PREVIEW OR ADD' and includes only essential details like membership verification and default preview. Every sentence contributes value with no redundancy.

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 core purpose and preview default but omits important context: what 'confirmed' does, what the preview output looks like, prerequisites, and post-add effects. Without an output schema, these gaps matter for a mutation-capable 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%, so the description must compensate. It explains 'preview' and 'leader' indirectly, but does not clarify the 'confirmed' parameter or provide explicit meaning for stableId and contractId beyond their names. This is insufficient for a 5-parameter tool.

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 'PREVIEW OR ADD an active player-company contract to a stable, optionally as a leader,' identifying the action and target resource. It distinguishes this tool from siblings like pws_remove_stable_worker and pws_get_stables.

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 gives implicit context via 'Verifies membership. Defaults to preview.' but does not explicitly state when to use this tool over alternatives or when not to use it. It suggests a safe preview default but lacks clear exclusions or alternative recommendations.

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