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

With no annotations provided, the description carries the behavioral burden and does well by disclosing the found=false fallback when no report was written and clarifying that the content is stored as an ordinary semantic memory page. It does not cover auth, rate limits, or explicit read-only guarantees, but for a parameterless report getter the disclosed behavior is adequate.

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 compact and front-loaded, with the key purpose in the first sentence and supporting behavioral details in the next two. Every sentence adds distinct value: scope, return behavior, and relationship to memory_recall. No filler 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?

Given the tool has no parameters, an output schema is present, and the behavior is simple read-only retrieval, the description covers everything needed to call it correctly. It explains what is returned, what happens when nothing was written, and how the note relates to the broader memory system.

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 tool has zero parameters and the schema description coverage is 100%, so there is no parameter information for the description to meaningfully add. The baseline for zero-parameter tools is 4, and the description appropriately focuses on behavior rather than parameter semantics.

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 opens with a specific verb-object pair: 'Latest nightly dream report for this org (what changed overnight)', clearly identifying the resource and scope. It further distinguishes itself by noting the report is also a normal semantic memory page that memory_recall can find, which positions this tool as the dedicated status view rather than a generic recall tool.

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 provides clear context: use this when you need the most recent nightly dream/change report for the org. It also mentions that the same note is discoverable via memory_recall, which indirectly signals a related alternative, though it does not explicitly state when to prefer one over the other.

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