ssh_set_review_mode

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

No annotations are present, so the description must disclose behavioral traits. It only says 'switch review mode' without explaining side effects, permission requirements, or whether the change is reversible. The meaning of each mode (off, whitelist, manual, smart) is not elaborated, leaving the agent without critical behavioral context.

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 a single, concise sentence that front-loads the action and option list. Every word earns its place; there is no wasted or irrelevant content.

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?

While the tool is simple (one enum parameter), the description omits necessary context about what each mode does and when to use it. Without an output schema, the agent still needs a basic understanding of the modes' effects to invoke the tool correctly. The one-line description is insufficient for choosing the right mode.

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 schema already defines the 'mode' parameter with an enum of the exact same values, so the description adds no semantic meaning. It merely repeats the enum list, and the phrase '可选' could be misinterpreted as 'optional' despite the parameter being required. This is a redundant and slightly misleading description of the parameter.

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 function with a specific verb ('switch') and resource ('review mode'), and lists the allowed options. This distinguishes it from siblings like ssh_get_review_mode, which is a read operation.

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 is provided on when to use this tool versus alternatives. It does not mention that ssh_get_review_mode is for reading the current mode, nor does it explain any prerequisites or context for setting a particular mode.

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