view_workspace

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

With no annotations, the description carries the load and does add genuine behavior: windows on other workspaces are hidden, not closed, which tells the agent this is non-destructive view switching. It omits what happens with an out-of-range index, whether set_workspace_count must precede it, or any permission/persistence notes.

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 sentences, zero waste, with the indexing convention and the hidden-not-closed behavior both front-loaded.

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 values need no explanation, and the tool is simple. Still, for a state-changing navigation tool with no annotations, the description leaves gaps around valid range and interaction with set_workspace_count.

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% and the single 'workspace' property has no description, so the description's 'numbered from 1' is the only source of indexing semantics. That is useful but incomplete — no upper bound, no interaction with workspace count.

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?

States a specific verb+resource ('Show a workspace') and clarifies the resource's indexing ('numbered from 1'). It does not name siblings like move_window_to_workspace or set_workspace_count, but the purpose is unambiguous on its own.

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 on when to use this versus moving a window to a workspace or changing the workspace count. The agent must infer from sibling names alone that this only switches the current view.

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