get_or_create_workspace

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

Goes well beyond the annotations by spelling out the consequence of idempotency ('never makes a duplicate or changes an existing workspace'), the failure-free repeat-call guarantee, and the initial state of a new workspace (status 'created'). Since there is no output schema, disclosing the return shape { id, name, targetLabel, status, createdAt, updatedAt } is genuinely additive.

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?

Front-loads the core semantics, then the idempotency guarantee, then the return shape, then the when-to-use rule — all in four dense sentences with no waste. Every sentence 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 two-parameter mutation tool with no output schema, the description supplies the return fields, initial status, idempotency semantics, and usage condition. Nothing an agent needs to call this correctly is missing.

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%, so both parameters are already fully documented in the schema. The description adds no syntax, format, or edge-case detail about 'name' or 'targetLabel' beyond what the schema states, which is the expected baseline 3 when the schema does the heavy lifting.

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 ('Get a workspace by name, creating it first if it doesn't exist') and immediately differentiates from siblings by noting that most other tools create their workspace implicitly. An agent can tell exactly what this does and when it is the right call 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?

Explicitly gives both when-to-use and when-not-to-use: 'safe to call every time you start work on something' and 'you only need this to set a targetLabel or to get the id'. That is a clear routing rule against the many sibling tools that manage workspaces implicitly.

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