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

Annotations already indicate this is a mutating, non-idempotent, non-destructive operation. The description adds valuable context: ownership by the calling user, the lack of a default ruleset, and pass-through behavior for other fields. No contradiction with annotations.

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?

Three sentences, front-loaded with the core operation, then required fields, then a short pass-through note. Every sentence earns its place; there is no filler or repetition of schema/annotations.

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?

Given an empty input schema, the description covers ownership, required fields, and the no-default ruleset rule; output schema exists so return values do not need explanation. The phrase 'other fields pass through to imagine' is somewhat vague, leaving some ambiguity about accepted input structure.

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 zero documented properties, so the description carries the full burden of parameter education. It names the required parameters (name and ruleset) and notes that other fields pass through, but it does not specify types, formats, or how pass-through fields are represented.

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 a specific action and resource: 'Create a new adventure,' and adds ownership context ('owned by the calling user'). It clearly distinguishes this from sibling tools like imagine_create_adventure_page or imagine_create_world by naming the resource and its required fields.

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 gives clear conditions for invocation: name and ruleset are required because there is no app-wide ruleset default for adventures. It does not explicitly name alternatives or state when not to use this tool, so exclusion guidance is missing.

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