get_wake_up

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

Beyond annotations (readOnlyHint true, idempotentHint true), description reveals timeout behavior (hard-capped by memory.recall.timeoutMs), degraded empty payload on timeout, and cache-friendly split design. 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?

Two sentences pack all essential information: purpose, cache-split design, legacy flat option, timeout behavior, and degraded mode. No fluff, well-structured for quick agent parsing.

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?

Even without output schema, describes return shape (split vs flat), degradation behavior, and timeout handling. Complete for a context retrieval tool at session start.

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?

All parameters have schema descriptions; description adds defaults and context-specific behaviors (e.g., max_decisions default differs by shape, auto_mine default true, service_name scoping). Schema coverage 100% but description enriches meaning.

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 provides 'Compact orientation context (~300 tokens) for session start' and explains the split shape behavior, distinguishing it from sibling tools like get_session_resume or get_minimal_context.

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?

Explicitly states it's for session start and provides guidance on using cache_split for different shapes. Lacks explicit when-not-to-use but context is sufficient for typical usage.

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