dream

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

With no annotations, the description carries the burden of explaining behavior. It does disclose the core behavior: hybrid search across multiple layers and context construction. However, it does not reveal side effects, permissions, rate limits, or what 'context construction' concretely entails.

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 a compact single sentence that front-loads the main behavior. The phrase 'Universal Primitive' is somewhat vague and adds little, but overall there is no unnecessary verbiage or buried structure.

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?

The description is too sparse for a tool with five parameters, no annotations, and no parameter documentation. It does not explain how to choose intent, layer, limit, or user_id, nor does it offer enough context to differentiate dream from its siblings. The presence of an output schema reduces some burden, but invocation guidance remains inadequate.

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 description coverage is 0%, and the description does not explain any of the five parameters (query, layer, limit, intent, user_id). The mention of layers refers to L3/L4/Wiki/Graph, not the 'user'/'agent' values of the layer parameter, so it provides no practical parameter guidance.

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 performs a hybrid search across all layers (L3, L4, Wiki, Graph) and that it constructs context. This is a specific action with a defined scope, though it does not explicitly contrast itself with sibling tools like think or forget.

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 tagline 'Universal Primitive' gestures at broad applicability, but there is no explicit guidance on when to use dream versus think, forget, evolve, or project. No exclusions, prerequisites, or alternative selection criteria are provided.

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