get_or_create_workspace

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

With no annotations provided, the description carries the behavioral disclosure burden. It meaningfully discloses that the call is idempotent and safe to repeat, which is the most important behavioral trait for a get-or-create tool. It does not detail side effects like permissions or storage, but the core repeat-safe behavior is covered.

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?

A single sentence with no filler. The core operation and the most important behavioral guidance are front-loaded, making it easy for an agent to grasp quickly.

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 two-parameter tool with no output schema, the description covers invocation context and repeatability adequately. It does not specify the return value or describe what 'workspace' means, but these are relatively minor given the tool's simplicity and the clarity of the get-or-create pattern.

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 only 50%, so the description must partially compensate for the undocumented 'name' parameter; the phrase 'by name' does clarify that 'name' is the identifier. However, the description adds no meaning for 'targetLabel' beyond the schema's existing 'Defaults to the workspace name' explanation.

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 states the exact operation ('get or create a workspace by name') and the key behavioral property (idempotent). This clearly distinguishes it from sibling tools like list_workspaces, which only read, and chat_with_workspace, which operates within an existing workspace.

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 phrase 'safe to call every time you start working on something' gives an explicit context for when to use it. It does not name alternative tools or state when not to use it, but the idempotent get-or-create semantics make the usage context clear enough.

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