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

The description discloses that it is state-changing and occurs after MCP client authorization, adding context beyond the annotations (readOnlyHint=false, destructiveHint=false). It does not detail all side effects, but enough is provided for a create operation.

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 two sentences, directly stating purpose and key requirements. No fluff or redundancy.

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 create operation, the description covers the essential trigger, required field, and state-changing nature. It does not mention output or side effects, but these are not necessary given the tool's simplicity and lack of output schema.

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?

All four parameters have schema descriptions, and the tool description summarizes them (name required, plus slug, is_public, description). This adds minimal value beyond the schema, as it only restates what is already explicit.

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 states the tool creates a new documentation Space or knowledge base container, with a specific verb and resource. It distinguishes from sibling tools like create-space-document and create-space-item by focusing on the space itself.

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?

It explicitly says 'Use this when the user wants to create a new documentation Space', providing a clear trigger condition. It does not mention alternatives or when-not-to-use, but the context is straightforward.

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