wikijs_set_context_mode

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

No annotations are present, so the description alone must disclose behavior. It reveals only that the mode is switched; it does not state whether the change is persistent, affects subsequent operations, requires permissions, or returns a confirmation. This is thin disclosure for a state-changing tool.

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 short sentence that front-loads the action and lists the accepted modes without any filler. Every word earns its place for this simple API.

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?

Given the tool's simplicity, the schema plus description provide enough to make a correct call: one enum parameter with full schema documentation. However, with no annotations and no output schema, behavioral details like return value and side effects are absent, leaving the description only minimally complete.

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 100% and the single mode parameter already has an enum plus a descriptive label. The description merely repeats the three enum values and adds no additional meaning or usage syntax, so the baseline score of 3 applies.

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 uses a specific verb ('Switch') and resource ('context mode'), and enumerates the three valid modes, so an agent understands exactly what the tool operates on. It is clearly distinguishable from siblings like wikijs_get_context, wikijs_detect_context, and the initialization tools, even though no alternative is named explicitly.

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 intended use is implied by the verb: use this tool when the current context mode needs to be changed. There is no explicit guidance about prerequisites (e.g., whether a repository/workspace must already be initialized) or when to prefer this over wikijs_detect_context or wikijs_get_context.

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