Enable or disable Focus Mode and Wide Mode in the Markdown editor.
Controls Focus Mode and Wide Mode
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "view_mode_set"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| wide | No | Wide Mode | |
| focus | No | Focus Mode |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden for behavioral disclosure. It only says 'Controls', not whether it toggles, sets, or requires a document to be open. The agent cannot discern side effects or required permissions.
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 phrase with no wasted words. However, it may be too brief, sacrificing clarity for conciseness.
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 simplicity of the tool (two booleans, no output), the description is incomplete. It fails to explain the overall effect, prerequisites, or any behavior beyond stating the modes are controlled.
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 100% with each parameter labeled. The description adds no extra meaning beyond the parameter names; it does not explain what Wide or Focus Mode do, so value added is minimal.
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 it controls Focus Mode and Wide Mode, identifying the verb and resource. However, it does not differentiate from sibling tools like `theme_set`, which also controls a mode. The purpose is clear but lacks specificity about what these modes affect.
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. There is no mention of prerequisites, context, or exclusions, leaving the agent to infer usage entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.