mcp_engram_get_continuation_bundle

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

No annotations provided, so description must supply all behavioral info. It states the tool is read-only ('without starting a session'), returns specific data, and mentions a wake-up optimization. It does not contradict any annotations (none exist) and gives a clear picture of what happens.

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, each serving a distinct purpose: what the tool returns, when to use it, and an optimization note. Could be slightly more concise but remains focused and front-loaded.

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?

No output schema is provided, and while the description mentions what the bundle contains (primary goal, active tiles/helpers, handoff lineage), it lacks details on the structure or format of the returned data. For a tool with no output schema, more explicit description of the return value shape would be beneficial.

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?

Input schema has zero parameters, so the description need not add parameter details. Baseline 4 applies since there is nothing to explain, and the description does not mislead about parameters.

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 it returns the 'live continuation bundle' with specific components (primary goal, active tiles/helpers, handoff lineage) and explicitly says it does so 'without starting a session', distinguishing it from session-start tools like mcp_engram_session_start.

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?

Provides explicit usage timing: 'at TUI 63-65% before context compression' and 'the VERY FIRST step in lean ritual for instant hot/legominism rehydration'. It implies alternative usage (don't use if you want to start a session) but does not explicitly list sibling tools except implicitly.

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