workspace_create

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds that ttl_minutes is clamped to the maximum configured TTL and that the response includes expiration time, but it omits details about mode behavior, side effects, failure modes, or cleanup responsibilities.

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 three sentences, front-loads the main purpose, and contains no redundant or filler content. Every sentence adds information.

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?

Despite an output schema, the description is incomplete for an agent: it doesn't explain the 'mode' parameter, doesn't indicate when workspace creation is appropriate, and doesn't clarify how this tool interacts with workspace_destroy. Given the two optional parameters and no annotations, more context is needed.

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?

The input schema has no per-property descriptions (0% coverage), so the description must explain the parameters. It only addresses ttl_minutes by explaining the clamping behavior; mode is completely unexplained, leaving the agent without enough information to choose a correct value.

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 opens with "Create a new workspace and return its identifier," which clearly states the action, resource, and expected return. This distinguishes it from workspace_destroy and other repo tools, though it doesn't explicitly contrast with them.

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 usage for workspace creation but provides no explicit when-to-use or when-not-to-use guidance. The note about TTL clamping is a parameter hint, not usage context, and no alternative tools are mentioned.

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