enable_review_mode

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

With no annotations provided, the description carries the full burden. It discloses the persistent effect ('every future AI reply you send here will need the owner's approval'), the duration ('until a human turns it back off'), and the limitation ('you cannot turn it off yourself').

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 somewhat verbose with parenthetical clarifications and repeated contrasts, but it remains focused and each clause adds meaningful information, so it is acceptable.

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 fully explains the action and its consequences, and since there is no output schema, no return-value documentation is needed. It covers the key operational context an agent would need.

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 input schema has no descriptions for session_id or reason, and the description does not explicitly explain these parameters. It implies session_id by referring to 'THIS session' but never clarifies the meaning or required format of reason, leaving a notable gap.

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's purpose: 'Turn on always-hold review mode for THIS session only' and explicitly contrasts it with demoting the whole listing to tier 1, distinguishing it from potential alternative actions.

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?

It provides explicit usage guidance: 'Use this when you decide a specific conversation needs human oversight' and specifies when not to use it: 'rather than demoting your whole listing to tier 1, which would slow down every other conversation too.'

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