notion_list_workspaces

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

With no annotations, the description carries the behavioral disclosure burden. It openly identifies the data source as a local cache, which implies a read-only, local operation and possible staleness. It does not detail freshness or authentication expectations, but for a parameterless list tool this is reasonably transparent.

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 front-loaded sentence with a clear verb and object. It contains no filler, redundant qualifiers, or schema repetition, and every word earns its place.

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?

For a simple no-parameter list tool, the description is mostly sufficient, but there is no output schema to compensate for the lack of return-value detail. It does not specify whether the result includes workspace names, IDs, or both, and the 'cached' behavior is only briefly implied. Still, the intended action is understandable.

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?

There are zero parameters, so the empty schema already captures everything structurally. The description adds useful context by explaining that the operation draws from cached data on this Mac, which helps an agent understand why no workspace argument is needed.

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 identifies the operation ('Lists') and the resource ('Notion workspaces'), and the qualifier 'cached on this Mac' distinguishes this from related tools like notion_list_databases and notion_list_pages. An agent can understand exactly what this tool does without opening the schema.

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 the tool should be used—when a list of cached Notion workspaces is needed—but it does not explicitly state when to prefer it over sibling tools or mention alternatives. There are no exclusions or routing cues beyond the workspace-specific wording, so the agent must infer the usage context.

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