notion_switch_workspace

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

No annotations exist, so the description carries the full load. It does disclose a meaningful behavioral trait — this mutates shared UI/session state and the agent is expected to notify the user and restore the prior workspace. It says nothing about what happens if the name is unknown, whether credentials/session change, or how subsequent calls are affected.

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, front-loaded with the action and followed by the workflow obligation. Nothing is padded, though 'switch back when done' is slightly vague about what 'done' means.

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?

With no annotations, no output schema, and an undocumented parameter, the description covers the core action and the restore obligation but omits failure behavior and side effects on the session. For a state-changing tool this leaves real gaps an agent would want filled.

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?

One required parameter ('name') with 0% schema description coverage, so the schema contributes nothing. The description clarifies that the value is a workspace/account name, which is genuinely useful, but gives no format, casing, matching rules, or example.

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 and resource: 'Switch the Notion window to another workspace/account by name.' That is clear and distinct from all listed siblings (launch, open, read, etc.), none of which change workspace context. It stops short of explicitly naming a sibling it differs from, so a 4 rather than a 5.

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 description implies when this is needed (when work must happen in a different workspace/account) and adds a lifecycle instruction: tell the user, and switch back when done. But it names no alternative tool and gives no precondition or failure guidance, so usage is only implied.

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