Create a draft cheese game by specifying the engine ID and version, and optionally add title, description, config, and ingredients.
Create a draft cheese (game). Requires engineId, engineVersion; optional title, description, config, ingredients.
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | ||
| config | No | ||
| engineId | Yes | ||
| description | No | ||
| ingredients | No | ||
| engineVersion | Yes |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description is minimal. It does not disclose side effects, return behavior, persistence, validation, permissions, or whether the draft is immediately usable.
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?
One concise, clear sentence with no unnecessary detail or repetition.
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?
No output schema or return behavior is described, and the tool lacks enough context for an agent to know what happens after creation or how to handle the response. Parameter meaning is also underspecified.
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 descriptions are absent, and the description only lists required/optional parameters without explaining what engineId, engineVersion, config, or ingredients mean or how they should be used.
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 action ('Create a draft cheese') and clarifies 'cheese (game)'. The word 'draft' distinguishes it from publish_cheese and other sibling tools.
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 a draft creation versus publishing, but it does not explicitly state when to use this tool or mention alternatives. No direct when-to-use or when-not-to-use guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.