Hub Pause

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

With no annotations, the description carries the full burden. It does disclose real behavioral detail absent from structured data: guests are cut off and receive the canned message 'the studio is paused', and the `why` text surfaces in hub_status. It says nothing about authorization (who may pause), persistence across restarts, or what happens to in-flight work, which are significant for a global kill switch.

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?

Two short clauses, with the identity ('The kill switch') front-loaded and the parameter notes attached inline. The telegraphic 'why:' fragment is slightly awkward but it is tight and wastes nothing.

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?

An output schema exists, so return details needn't be spelled out, and the description covers the core effect and its reversal. For a global, no-annotation kill switch it should still say whether permission is required and whether the pause survives a restart or a hub_stop.

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 coverage is 0%, so the description must compensate, and it does: `off` is given meaning via 'until hub_pause(off=True)', and `why` is defined as 'a few words, shown in hub_status'. Both of two parameters gain semantics beyond the bare schema, though the `off` naming remains mildly counterintuitive.

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?

It identifies the resource (the hub) and characterizes it as 'the kill switch', and states the effect on guests ('guests get "the studio is paused"'). However, 'every place answers only the owner' is cryptic, and the polarity of the tool is only inferable from the parenthetical '(off=True)', which suggests the no-argument call pauses everything. An agent can guess the intent but not describe it confidently.

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 parenthetical 'until hub_pause(off=True)' is effectively a reversal hint, which is the most useful usage cue here. There is no statement of when to pause versus using the sibling hub_stop, nor any exclusion or prerequisite, so usage is implied rather than prescribed.

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