dream_run_now

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

No annotations are provided, so the description carries full burden. It states it runs a cycle and returns results, which is moderately transparent. However, it does not mention side effects, blocking nature, performance impact, or prerequisites, leaving some behavioral aspects unclear.

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 concise sentences. The first sentence states the action and immediacy, the second describes the return value. No unnecessary words.

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 the tool's simplicity (one parameter, no output schema), the description is adequate but incomplete. It mentions 'detailed per-phase results' but does not specify output format or structure. Since there is no output schema, the description could have been more informative about the return.

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 100% coverage with descriptions for each boolean property. The tool description adds minimal value beyond the schema, only hinting at 'per-phase' control. Baseline 3 is appropriate since the schema is already well-documented.

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 action ('Run a single dream cycle immediately') and the resource ('dream cycle'), and mentions the return value ('Returns detailed per-phase results'). This distinguishes it from siblings like dream_start, which likely starts a long-running cycle.

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 (run one cycle immediately) but does not explicitly state when to use this tool over alternatives such as dream_start, run_consolidation_now, or other cycle-related siblings. No 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.